Signature-based cache optimization for data preparation

ABSTRACT

Signature-based cache optimization for data preparation includes: performing a first set of sequenced data preparation operations on one or more sets of data to generate a plurality of transformation results; caching one or more of the plurality of transformation results and one or more corresponding operation signatures, a cached operation signature being derived based at least in part on a subset of sequenced operations that generated a corresponding result; receiving a specification of a second set of sequenced operations; determining an operation signature associated with the second set of sequenced operations; identifying a cached result among the cached results based at least in part on the determined operation signature; and outputting the cached result.

CROSS REFERENCE TO OTHER APPLICATIONS

This application is a continuation of co-pending U.S. patent applicationSer. No. 14/883,582, entitled SIGNATURE-BASED CACHE OPTIMIZATION FORDATA PREPARATION filed Oct. 14, 2015 which is incorporated herein byreference for all purposes.

BACKGROUND OF THE INVENTION

When evaluating data, operator-users often wish to try performingdifferent operations on the data to see what different results mightemerge. Typically, re-computation is performed on the data. For largescale web applications, which may have millions or even billions ofrecords, this can be computationally intensive, which can lead to slowapplication response times.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a functional diagram illustrating a programmed computer systemfor performing signature-based cache optimization for data preparationin accordance with some embodiments.

FIG. 2 is a system diagram illustrating an embodiment of a system fordata preparation.

FIG. 3 is a system diagram illustrating an embodiment of a pipelineserver.

FIG. 4 illustrates an example embodiment of a three-part function.

FIG. 5 is a flow diagram illustrating an example embodiment of a processfor partitioning.

FIG. 6A illustrates an example embodiment of a script.

FIG. 6B illustrates an example embodiment of a data set to be processed.

FIG. 7A illustrates an example embodiment of data structures generatedduring an import operation.

FIG. 7B illustrates an example embodiment of executing a data traversalprogram.

FIG. 8A illustrates an example embodiment of an updated data traversalprogram.

FIG. 8B illustrates an example embodiment of executing a data traversalprogram.

FIG. 9A illustrates an embodiment of a process for updating a datatraversal program to reflect the results of a filter operation.

FIG. 9B illustrates an example embodiment of a data traversal program.

FIG. 10A is a diagram illustrating an embodiment of a data set to besorted.

FIG. 10B is a diagram illustrating an embodiment of data traversalprograms and file sets.

FIG. 10C illustrates an example of a sorted result.

FIG. 10D is a diagram illustrating an embodiment of a process forperforming a sort operation.

FIG. 10E illustrates an example embodiment of data traversal programs.

FIG. 10F illustrates an example embodiment of a native Spark sort.

FIG. 11A illustrates an example embodiment of a script including anappend operation.

FIG. 11B illustrates an example embodiment of data sets to be appended.

FIG. 11C illustrates an example embodiment of logical file/name spacesassociated with pipelines for two different data sets.

FIG. 11D illustrates an example embodiment of data traversal programsprior to an append.

FIG. 11E illustrates an example embodiment of data traversal programssubsequent to an append.

FIG. 11F illustrates an example embodiment of partitions and datatraversal programs.

FIG. 11G illustrates an example embodiment of data traversal programsprior to an append.

FIG. 11H illustrates an example embodiment of data traversal programssubsequent to an append.

FIG. 11I illustrates an example embodiment of data traversal programsand file sets.

FIG. 11J illustrates an example embodiment of a tree representation of aset of sequenced operations.

FIG. 11K illustrates an example embodiment of a tree representation of aset of sequenced operations.

FIG. 12A illustrates an example of data sets to be joined.

FIG. 12B illustrates an example of data traversal programs and file setsgenerated for imported data.

FIGS. 12C-E illustrate an example embodiment of a process for performinga join.

FIG. 12F illustrates an example embodiment of data traversal programsprior to a join.

FIG. 12G illustrates an example embodiment of data traversal programssubsequent to a join.

FIG. 13 is a flow diagram illustrating an embodiment of a process forcaching transformation results.

FIG. 14 is a flow diagram illustrating an embodiment of a process forcache reuse.

FIGS. 15A-E illustrate example embodiments of user interfaces of a stepeditor.

FIG. 16 is a flow diagram illustrating an embodiment of a process forusing a step editor for data preparation.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Using the techniques described herein, a distributed computing platformsuch as Apache Spark™ can be efficiently utilized to perform sequenceddata preparation operations (i.e., a set of operations that are appliedin sequential order) on data sets to generate transformation results. Asused herein, a data preparation operation refers to an operation used totransform/mutate an input data. The input data is accessible dynamicallyupon execution of a set of sequenced operations, where the data is notnecessarily stored, but may be computed on-the-fly, as needed. This isin contrast to operating against data stored at a fixed and knownlocation, and is performed without the advantages of prior indexing andpartitioning. The input data includes data that is organized (e.g., intorows and columns). Various examples of data preparation operationsinclude clustering, joining, appending, sorting, uppercase, lowercase,filtering, deduplicating, grouping by, adding or removing columns,adding or removing rows, pivoting, depivoting, order dependentoperations, etc. The representation of the transformation results isreferred to herein as a “data traversal program,” which indicates how toassemble one or more affected columns in the input data to derive atransformation result. The representation of the transformation resultscan be stored for reuse along with corresponding operation signatures,allowing cached results to be identified and obtained for reuse.

Cache optimization using signatures is disclosed. In some embodiments, afirst set of sequenced data preparation operations on one or more setsof data to generate a plurality of transformation results is performed.One or more of the transformation results and corresponding operationsignatures are stored. A stored operation signature is derived based atleast in part on a subset of sequenced operations that generated acorresponding result. At a later time, when a specification of a secondset of sequenced operations is received, an operation signatureassociated with the second set of sequenced operations is determined. Astored result is identified using the determined operation signature.The stored result is then outputted.

FIG. 1 is a functional diagram illustrating a programmed computer systemfor performing signature-based cache optimization for data preparationin accordance with some embodiments. As will be apparent, other computersystem architectures and configurations can be used to perform automatedjoin detection. Computer system 100, which includes various subsystemsas described below, includes at least one microprocessor subsystem (alsoreferred to as a processor or a central processing unit (CPU)) 102. Forexample, processor 102 can be implemented by a single-chip processor orby multiple processors. In some embodiments, processor 102 is a generalpurpose digital processor that controls the operation of the computersystem 100. Using instructions retrieved from memory 110, the processor102 controls the reception and manipulation of input data, and theoutput and display of data on output devices (e.g., display 118). Insome embodiments, processor 102 includes and/or is used to providepipeline server 206 of FIG. 2 and/or executes/performs process 500,1300, 1400, and/or 1600.

Processor 102 is coupled bi-directionally with memory 110, which caninclude a first primary storage, typically a random access memory (RAM),and a second primary storage area, typically a read-only memory (ROM).As is well known in the art, primary storage can be used as a generalstorage area and as scratch-pad memory, and can also be used to storeinput data and processed data. Primary storage can also storeprogramming instructions and data, in the form of data objects and textobjects, in addition to other data and instructions for processesoperating on processor 102. Also as is well known in the art, primarystorage typically includes basic operating instructions, program code,data, and objects used by the processor 102 to perform its functions(e.g., programmed instructions). For example, memory 110 can include anysuitable computer-readable storage media, described below, depending onwhether, for example, data access needs to be bi-directional oruni-directional. For example, processor 102 can also directly and veryrapidly retrieve and store frequently needed data in a cache memory (notshown).

A removable mass storage device 112 provides additional data storagecapacity for the computer system 100, and is coupled eitherbi-directionally (read/write) or uni-directionally (read only) toprocessor 102. For example, storage 112 can also includecomputer-readable media such as magnetic tape, flash memory, PC-CARDS,portable mass storage devices, holographic storage devices, and otherstorage devices. A fixed mass storage 120 can also, for example, provideadditional data storage capacity. The most common example of massstorage 120 is a hard disk drive. Mass storages 112, 120 generally storeadditional programming instructions, data, and the like that typicallyare not in active use by the processor 102. It will be appreciated thatthe information retained within mass storages 112 and 120 can beincorporated, if needed, in standard fashion as part of memory 110(e.g., RAM) as virtual memory.

In addition to providing processor 102 access to storage subsystems, bus114 can also be used to provide access to other subsystems and devices.As shown, these can include a display monitor 118, a network interface116, a keyboard 104, and a pointing device 106, as well as an auxiliaryinput/output device interface, a sound card, speakers, and othersubsystems as needed. For example, the pointing device 106 can be amouse, stylus, track ball, or tablet, and is useful for interacting witha graphical user interface.

The network interface 116 allows processor 102 to be coupled to anothercomputer, computer network, or telecommunications network using anetwork connection as shown. For example, through the network interface116, the processor 102 can receive information (e.g., data objects orprogram instructions) from another network or output information toanother network in the course of performing method/process steps.Information, often represented as a sequence of instructions to beexecuted on a processor, can be received from and outputted to anothernetwork. An interface card or similar device and appropriate softwareimplemented by (e.g., executed/performed on) processor 102 can be usedto connect the computer system 100 to an external network and transferdata according to standard protocols. For example, various processembodiments disclosed herein can be executed on processor 102, or can beperformed across a network such as the Internet, intranet networks, orlocal area networks, in conjunction with a remote processor that sharesa portion of the processing. Additional mass storage devices (not shown)can also be connected to processor 102 through network interface 116.

An auxiliary I/0 device interface (not shown) can be used in conjunctionwith computer system 100. The auxiliary I/O device interface can includegeneral and customized interfaces that allow the processor 102 to sendand, more typically, receive data from other devices such asmicrophones, touch-sensitive displays, transducer card readers, tapereaders, voice or handwriting recognizers, biometrics readers, cameras,portable mass storage devices, and other computers.

In addition, various embodiments disclosed herein further relate tocomputer storage products with a computer readable medium that includesprogram code for performing various computer-implemented operations. Thecomputer-readable medium is any data storage device that can store datawhich can thereafter be read by a computer system. Examples ofcomputer-readable media include, but are not limited to, all the mediamentioned above: magnetic media such as hard disks, floppy disks, andmagnetic tape; optical media such as CD-ROM disks; magneto-optical mediasuch as optical disks; and specially configured hardware devices such asapplication-specific integrated circuits (ASICs), programmable logicdevices (PLDs), and ROM and RAM devices. Examples of program codeinclude both machine code, as produced, for example, by a compiler, orfiles containing higher level code (e.g., script) that can be executedusing an interpreter.

The computer system shown in FIG. 1 is but an example of a computersystem suitable for use with the various embodiments disclosed herein.Other computer systems suitable for such use can include additional orfewer subsystems. In addition, bus 114 is illustrative of anyinterconnection scheme serving to link the subsystems. Other computerarchitectures having different configurations of subsystems can also beutilized.

FIG. 2 is a system diagram illustrating an embodiment of a system fordata preparation. The system includes front end 200 and pipeline server206.

Front end 200 is configured to provide an interface for configuring datapreparation. Front end 200 interacts with the pipeline server 206. Invarious embodiments, front end 200 can be implemented as a standaloneapplication and/or a browser-based client application executing on aclient device and communicating with the pipeline server, as a J2EEapplication server such as Tomcat or Jetty, or a combination thereof.Front end 200 includes user interface engine 202 and script generator204.

User interface engine 202 is configured to interact with pipeline server206 to present table data, configuration options, results of sequencedoperations, and any other appropriate information to the user in userinterface screens and receive user input from user interface components.For example, user interface engine 202 is configured to provide editoruser interfaces by which users can specify a sequence of datapreparation operations to be performed on one or more sets of data togenerate one or more transformation results. The specified sequenced setof operations, which are to be applied in a specified order, forms apipeline through which one or more sets of data are processed. The datasets include tables of data that include data records organized in rowsand columns. Examples of user interfaces provided by user interfaceengine 202 are described in conjunction with FIGS. 15A-E.

Script generator 204 is configured to generate a script based on thedata sets and sequence of operations specified by a user using the onemore user interfaces provided by user interface engine 202. The scriptincludes a formatted set of instructions that includes a specificationof the one or more data sets to be operated on and the sequenced set ofoperations specified to be performed on the one or more data sets. Insome embodiments, the pipeline specified in the script is referred to asan application. An example of a script generated using script generator204 is described in conjunction with FIG. 6A.

Pipeline server 206 is configured to perform data preparation. In someembodiments, the pipeline server receives a script from script generator204, and performs a sequenced set of data preparation operations (whichform a pipeline) on one or more input data sets (e.g., data sets 214)according to the script. A data set can be stored in a memory (e.g., arandom access memory), read or streamed from a storage (e.g., a localdisk, a network storage, a distributed storage server, etc.), orobtained from any other appropriate sources. Pipeline server 206 can beimplemented on one or more servers in a network-based/cloud-basedenvironment, a client device (e.g., a computer, a smartphone, a wearabledevice, or other appropriate device with communication capabilities), ora combination. In some embodiments, the pipeline server is deployed asan application. The pipeline server can be implemented using a systemsuch as 100. In some embodiments, the pipeline server is implementedusing a distributed computing platform, such as Apache Spark™. Whileexample embodiments involving Apache Spark™ are described below, anyother distributed computing platform/architecture can be used, with thetechniques described herein adapted accordingly. Pipeline server 206includes data partitioning engine 208, data transformation engine 210,and caching engine 212.

Data partitioning engine 208 is configured to partition input data sets(e.g., data sets 214) and distribute them to a cluster of processingnodes in a distributed computing environment. In some embodiments, thedata partitioning engine is configured to pre-process the input data sothat it can be translated into a form that can be provided to adistributed computing platform such as Apache Spark™. Determining thedistribution of the data in a data set includes determining how obtaineddata sets should be divided/partitioned into logical partitions/workportions, and includes determining how many partitions should begenerated, as well as the load to assign each partition. In someembodiments, the partition determination is based on various costfunctions. The operations of the data partitioning engine are describedin greater detail below.

Data transformation engine 210 is configured to perform datapreparation. Performing data preparation includes determiningtransformation results by performing a sequenced set of data preparationoperations on one or more sets of data. In some embodiments, the datatransformation engine is a columnar data transformation engine. In someembodiments, the data transformation engine is also configured toperform caching of results, as well as lookups of existing cachedresults for reuse.

As will be described below, the data transformation engine is configuredto efficiently perform the sequenced data preparation operations bygenerating a compact representation (referred to herein as a “datatraversal program”) of the transformation results of a set of sequencedoperations on one or more sets of data. The data traversal programincludes references and reference stacks which, when used in conjunctionwith column files, indicate how to assemble one or more affected columnsin the one or more sets of data that were operated on to derive atransformation result. The operations of the data transformation engineare described in greater detail below.

Caching engine 212 is configured to perform caching and cacheidentification. For example, the data traversal program/representationof the results determined using data transformation engine 210 can becached at various points (e.g., after a particular subset of sequenceddata preparation operations) for reuse. The data being cached can bestored in a cache layer, for example in memory (e.g., random accessmemory), stored on a local or networked storage device (e.g., a disk ora storage server), and/or any other appropriate devices. The results canbe cached, for example, based on an explicit request from a user (e.g.,via an interaction with a step editor user interface provided by userinterface engine 202). The results can also be cached automatically, forexample, based on factors such as the complexity of operations that wereperformed to arrive at the result. The cached representations can beidentified based on corresponding signatures. For example, the cachingengine can take as input a set of sequenced operations (e.g., receivedin a script generated from user input via step editor user interfacesprovided by user interface engine 202), derive an operation signature,and compare it to the signatures associated with existing cachedresults. The operations of the caching engine are described in greaterdetail below.

FIG. 3 is a system diagram illustrating an embodiment of a pipelineserver. In some embodiments, pipeline server 300 is an example ofpipeline server 206 of FIG. 2. In this example, pipeline server 300 isimplemented using a distributed computing platform. In some embodiments,the distributed computing platform of pipeline server 300 is used toimplement data partitioning engine 208, data transformation engine 210,and caching engine 212 of FIG. 2.

Shown in pipeline server 300 is an example embodiment of a Sparkcluster. The cluster includes a Spark master (302) and Spark workers(304 and 312). In some embodiments, the Spark cluster is implementedusing a master-slave architecture. In some embodiments, the Spark masteris configured to coordinate all work that is to be executed (in possiblya distributed manner). In some embodiments, the Spark workers areresponsible for receiving and executing pieces of work that point atsome data with instructions as to the operations to perform. The Sparkmaster and workers can be implemented, for example, as Javaapplications.

In some embodiments, the Spark master is configured to receive requests(e.g., jobs) from external clients. The Spark master is configured tobreak down the job into smaller chunks (work portions) and distributethe work to the various Spark workers. When a Spark worker completes itsportion of the work, it returns the results to the Spark master. Onceall of the workers return their respective results, the Spark mastercompiles all of the worker results and returns the final result to therequesting client.

In some embodiments, when run in a standalone mode, the Spark master isconfigured to track the health/status of the workers manage workscheduling.

In some embodiments, both the Spark master and workers use a companionapplication (e.g., a purpose-built Spark application) to perform theactual work. In some embodiments, the companion application runs on allof the machines that run a Spark process (both Master and workers). Therun-time instance of the companion application (also referred to hereinas a “pipeline” application) that runs on the worker machine is referredto herein as a Spark “pipeline executor.” A Spark worker is configuredto perform its job through the executor application.

In this example, while two Spark workers are shown, any number of Sparkworkers may be established in the cluster. In some embodiments, anapplication (e.g., data preparation application initiated by a front endsuch as front end 200) provisions the cluster of nodes to perform a setof sequenced operations comprising a pipeline through which data setsare pushed. In some embodiments, each Spark master or worker is a nodecomprising either a physical or virtual computer, implemented in variousembodiments as a device, a processor, a server, etc.

In this example, the Spark master is designated to communicate with a“pipeline master” (308), and the Spark workers are designated tocommunicate with pipeline executors (310 and 306). The pipelinemasters/executors connect with Spark software residing on theircorresponding nodes.

As described above, the pipeline server receives a script that specifiesone or more input data sets and a set of sequenced data preparationoperations that form a pipeline through which the input data sets are tobe processed. The pipeline server, using the distributed computingplatform, processes the input data according to the received script.

Data Partitioning

In this example, the pipeline master is configured to performpartitioning of the input data sets. In some embodiments, the pipelinemaster is used to implement data partitioning engine 208 of FIG. 2.Partitioning includes dividing a data set into smaller chunks (e.g.,dividing a data set with one hundred rows into five partitions withtwenty rows each). In some embodiments, the set of data is divided intowork portions, or pieces of work that are to be performed. The pipelinemaster is also configured to distribute the partitions to the variousestablished pipeline executors in the provisioned cluster forprocessing. In a Spark implementation, a division/partition (alsoreferred to as a “portion of work” or “work portion”) of the data set isrepresented as a Resilient Distributed Dataset (RDD). Other partitionformats are possible for other distributed platform implementations.

When partitioning data, various tradeoffs exist when determining howmany partitions to create and/or how many rows/how much to include ineach partition. For example, while an increase in the number of slicesof data can lead to an increase in parallelism and computation speed,the increased number of partitions also results in increased overheadand increased communication bandwidth requirement, due to data having tobe communicated back and forth between an increasing number of nodes.This can result in inefficiencies. Using the techniques describedherein, partitioning can be optimized. For example, an optimal number ofpartitions and/or an optimal size/number of rows per partition can bedetermined.

The master node is configured to devise or consume an intelligentstrategy to partition a data set by taking into consideration variouspieces of information. In various embodiments, the consideredinformation includes information about the data being operated on, thedata preparation operations to be performed, the topology/performancecharacteristics of the distributed computing environment, etc. Byconsidering such information, a partitioning strategy can be devisedthat optimizes, for example, for reliable throughput throughout thenodes of a cluster so that the nodes can complete processing atapproximately the same time. Thus, for example, straggling in thedistributed computing environment can be reduced (e.g., where someworkers are spending more time performing their portion of the work ascompared to other workers, and must be waited upon).

The information about the data being operated on includes metadatainformation about the data. In one example embodiment, the Spark(pipeline) master queries an input data set (e.g., obtained from asource location described in a received script). The pipeline masterprobes the data set to determine metadata describing the data set. Invarious embodiments, the metadata includes the number of rows that arein the data set, the number of columns that are in the data set, etc. Insome embodiments, the metadata that is determined/generated includesstatistical information, such as histogram information about how data isdistributed within the data set. For example, it may be determined thatsome rows in the data set are denser than others. The metadatadetermined as a result of the analysis (e.g., statistical analysis) isused in part by the pipeline master to devise an intelligentpartitioning strategy.

Example embodiments of partitioning strategies are described below.

Example Strategy 1: Partitioning Based on Row Count

In this example strategy, a data set is divided based on row count, sothat in this context-free approach (e.g., where metadata informationabout the rows or other information is not utilized), each Sparkworker/pipeline executor is given a fixed (e.g., same) number of rows.In some embodiments, an assumption is made that each row will take thesame amount of resources and time to process.

Example Strategy 2: Partitioning Based on a Size of Rows/Amount of Data

In this example strategy, a data set is divided in part based on thesizes of the rows in the data set. A statistical analysis is performedon the data to determine the density and/or amount of the data in therows of the data set (e.g., the amount of data may vary from row torow). For example, metadata indicating the amount of space that a rowtakes is determined. The data set is divided in a manner such that eachpartition includes the same amount of data (but may include varyingnumbers of rows).

In some embodiments, the number of rows is utilized as a secondarycriterion in addition to the size of the rows. For example, a number ofrows that has a data size of a given amount is determined for apartition. If the number of rows exceeds a threshold number of rows (oris more than a threshold number of deviations away from a mean number ofrows), then the number of rows in the partitions is trimmed, and cappedat the threshold. For example, each partition is assigned 100 MB of dataor 200,000 rows, whichever produces fewer rows.

The use of the number of rows as a secondary criterion is based in parton the columnar nature of the data transformation, where data istransformed based on data preparation operations performed with respectto a particular column or columns, and it is those columns which areaffected by the data preparation operations which determine the amountof computational effort needed to perform an operation. However, a rowincludes data cells in every column of a data set, and the size of therow may be concentrated in data cells that are in columns that do notmaterially contribute to the cost of an operation. By using a number ofrows as a secondary criterion, columns that have outlier distributionsin terms of size can be eliminated (assuming that most common datapreparations are operating on data that is fairly uniform indistribution). This provides a limiter for how much data will ultimatelybe processed in the distributed computing system.

In some embodiments, the limit/maximum number of rows per partition isdetermined as a function of the total number of rows for an entire dataset. An example plot illustrating an embodiment of a three-part functionis shown in FIG. 4. The slopes and transition points of the linesegments shown in the figure are empirically determined and may vary indifferent embodiments. In this example, for data sets whose number ofrows falls within range 402, partitions are loaded with a largerproportion of the total number of rows of the data set. For example, forvery small data sets, a single partition is loaded with all of the data.By doing so, data will not need to be distributed across partitions (andpotentially to different nodes), reducing resource overhead. Thus, inthis first region 402, for smaller input data sets, it is more efficientto divide the data set into fewer partitions; in other words, thepartitioning technique favors putting more rows into a single partition.

For data sets with a total number of rows in range 404, new partitionsare steadily added as the total number of rows are increased, where thesize of each partition grows steadily. In comparison to region 402, inregion 404, the rate at which rows are added to partitions is slower.For example, in this range, the addition of new partitions is favoredover adding rows to those partitions. While rows are still added topartitions steadily, which may sacrifice some partitions' performance ona node (as the node will have to process more row data), they are addedat a rate such that the number of partitions to be processed does notexpand too much.

For data sets whose total number of rows exceeds threshold 406, thenumber of rows that can be included in a partition is frozen and doesnot grow, where the addition of more partitions is favored. Thus, anupper bound on the number of rows that can be included in a singlepartition is established, allowing for the knowledge that each partitionwill be able to process a limited (upper-bounded) amount of data in arelatively fixed amount of time.

Example Strategy 3: Partitioning Based on a Size of Active Portions ofRows

In this strategy, as in strategy 2, an amount of data to include in apartition is considered. However, only the data in those columns thatare involved (i.e., active) in (or affected by) an operation (or set ofsequenced operations) is considered. For example, if, out of four totalcolumns, only three of those columns are involved in a data preparationoperation (e.g., a join operation that uses these three columns), thenonly the data in those three columns is determined. The data set is thenpartitioned according to the amount of data in the active columns (e.g.,as described above in strategy 2). In some embodiments, a density ofdata in the active portions of rows is used as another factor todetermine partitioning.

In some embodiments, strategies 2 and 3 are context aware, and take intoaccount attributes and characteristics of the data set to be processed(e.g., metadata information determined about the rows of the data set).In some embodiments, the context aware strategies also take into accountthe physical characteristics of the cluster, such as the amount ofmemory that a partition will require and the amount of memory that apipeline executor working on a partition can accommodate. For example,the amount (memory size) of data that can be in a partition can be setso that it does not exceed the memory that an executor is allocated touse. Other physical characteristics of the cluster that are taken intoaccount include performance metrics such as an amount of processingpower, network bandwidth metrics, etc., as will be described in furtherdetail below.

The nodes in a cluster may be physical machines with varying performancecharacteristics. For example, suppose that a cluster includes twocomputing nodes. The first has 8 processor cores, with 10 GB of memoryper core (i.e., a total of 80 GB of memory), while a second node has 16processor cores, also with 10 GB of memory per core (i.e., a total of160 GB of memory). Based on these memory/processing characteristics ofthe nodes, and using a heuristic in which a worker is allocated 10 GBper processor core, a number of workers that is a multiple of threeshould perform the work across the two nodes. This is because the firstnode has one-third of the total memory, while the second node hastwo-thirds of the total memory (i.e., the ratio of memory for the twonodes is 1:2), and having a number of workers that is a multiple ofthree will ensure that the total amount of memory in the cluster isfully utilized.

However, given that the nodes of the cluster may vary in performancecharacteristics, and that the cluster structure may change, in someembodiments, the creation of partitions is done without explicitknowledge of the actual processing capabilities of the cluster. Rather,each partition is allocated a pre-specified amount of computingresources, such as an amount of memory (e.g., 10 GB) per core. The dataset is then divided according to the performanceheuristic/characteristic (e.g., into chunks that are some multiple of 10GB). Thus, for example, if a partition is allocated a maximum of 10 GBof memory per core, then the first node, with 80 GB of total memoryacross 8 cores can support 8 partitions/workers (where one partitioncorresponds to one worker). In this example, the property of an amountof RAM per core has been reduced down to a principle/heuristic that canbe applied to tasks (and without explicit knowledge of the actualhardware of the cluster).

In some embodiments, a partition is processed by one worker, and theamount of resources that can be allocated to a partition/worker isembodied in an atomic computing unit, which defines the performancecharacteristics of a worker unit that can work on a partition. Theatomic computing unit is associated with a set of performance metricswhose values indicate the amount of resources that a worker/pipelineexecutor has to process the partition. In addition to an amount ofmemory per core, as described above, other properties that can bereduced down into this higher level form include network bandwidth,latency, and core performance. By defining a higher level view of theamount of resources available to a single worker unit (working on apartition), the cost in resources for adding partitions (and more workerunits) can be determined. For example, a cost function can be used todetermine, given a set of performance characteristics/heuristics, a costof computing a result. In some embodiments, a unit of cost is computed(e.g., for a worker to process some number of rows/amount of data). Thedata is then divided based on the computed unit of cost to determine anumber of workers needed to process the data.

Thus, using the higher level view of the performance characteristics ofan atomic worker unit, a number of workers needed to work on a data setcan be determined (i.e., the number of pieces of work/partitions intowhich the data should be divided). Additionally, the number ofpartitions/pieces of work to create versus the number of rows to add toa partition can be evaluated based on computation costs.

In some embodiments, the determination of how to partition a data set isbased on the characteristics of an operation to be performed. Forexample, different types of operations will have different computationalcosts. As one example, a function that takes a single input and providesan output solely based on that input, such as an uppercase operation,has a constant cost. Other types of operations, such as sort, which mayrequire partitions to communicate with each other, may have larger costs(e.g., order of log n divided by the number of partitions for sort). Adata set can then be partitioned based in part on the cost to performthe operations specified in a received script.

Any combination of the strategies and techniques described above can beused to determine a strategy for partitioning a data set according to acost function. In some embodiments, the partitions are contiguous andnon-overlapping. As one example, suppose that a data set of 200 rows,indexed from 0 to 199, is divided equally into four logical partitions(e.g., using strategy 1 described above). A first partition will haverows 0-49, a second partition will have rows 50-99, a third partitionwill include rows 100-149, and a fourth partition will include rows150-199. In some embodiments, the partitions are ordered as well, suchthat the rows obtained/read from partition N+1 follow the rowsobtained/read from partition N. Thus, a data set can be read in roworder by reading each partition in sequential order. The partitions arethen distributed to the pipeline executors/Spark workers in thedistributed computing deployment architecture. For example, a Sparkscheduler determines where (e.g., node) a partition/piece of work is tobe assigned and processed.

FIG. 5 is a flow diagram illustrating an example embodiment of a processfor partitioning. In some embodiments, process 500 is executed by datapartitioning engine 208 of FIG. 2. The process begins at 502 when aspecification of a set of sequenced operations to be performed on a setof organized data is received. In some embodiments, the sequencedoperations include data preparation operations. As one example, the setof data can be organized into rows and columns, or any other appropriatedimensions. The specification of the set of sequenced operations to beperformed on the set of organized data can be received in the form of ascript (e.g., generated based on user input via a step editor userinterface, imported from a file, etc.), as described above.

At 504, the set of data is divided into a plurality of work portionsbased on a cost function that is dependent on at least one dimension ofthe set of data. In some embodiments, the set of data is divided basedon a cost function that takes into account a number of rows to includein a work portion. The cost function can take into account variousfactors, such as an amount of data to be processed, the computationalcost of creating additional work portions/partitions, the cost to addrows to a partition/work portion, the computational cost of operationsto be performed, etc. Examples of techniques and strategies for dividinga set of data into a plurality of work portions/partitions are describedabove. If multiple data sets are specified in the specification, thedata sets can be divided into logical partitions in their own respectivenamespaces.

At 506, the plurality of work portions is distributed to a plurality ofprocessing nodes to be processed according to the specification ofoperations. For example, a scheduler (e.g., Spark scheduler) distributesthe determined work portions to processing nodes in a distributedcomputing cluster. In some embodiments, the determined work portions aresent to the processing nodes via a tree-structured description ofdependent operations to be performed on some input data. An example ofdependent operations is as follows: making a change to column A thatdepends on a change to column B that depends on a cache of columns A, B,and C.

The above described strategies and techniques for distributed pipelineoptimization provide various benefits. For example, as described above,a data set can be distributed to workers in an intelligent manner thattakes into consideration the characteristics of the data itself (e.g.,the amount of data in a row, the active columns in the row, etc.). Thisallows workers, for example, to process similar amounts of data,reducing the amount of time needed to wait for stragglers (e.g., thatare taking longer to compute their portion of work). As another example,by considering the physical characteristics of a cluster, work portionscan be generated that efficiently utilize the resources of the cluster.As another example, using the strategies described above, an optimalnumber of work portions and/or number of rows/amount of data to includein a work portion can be determined to minimize additional overhead andmaximize parallelism. Thus, distributed computing can be performed moreefficiently and predictably.

Data Transformation and Cache Optimization

Once an input data set has been partitioned and distributed, a set ofsequenced data preparation operations can be applied to the data setaccording to the specification of a received script. For example, thepipeline master 308, having divided one or more input data sets anddistributed them to workers/nodes in a distributed computing cluster, isconfigured to cooperate with the pipeline executors to determinetransformation results. In some embodiments, each pipeline executorworking on a partition/work portion is configured to provide a subset ofthe overall results of performing a sequenced set of operations. Thepipeline master has the responsibility of collating/combining the resultsubsets into the overall result. In some embodiments, the pipelinemaster of the cluster is used to implement data transformation engine210 and caching engine 212 of FIG. 2.

In some cases, distributed computing platforms such as Spark includenative functionality for performing various operations. However, themanner in which these platforms execute operations typically requiresdata to be replicated, which can be resource intensive and inefficient.

Using the techniques described herein, a set of sequenced operations canbe performed without replicating data at each stage of the pipeline,thereby increasing the speed and efficiency with which the sequenced setof operations can be performed and data transformation results obtained.An example illustrating how a platform such as Spark replicates datawhen performing an operation, in contrast to the techniques describedherein, will be shown with respect to the sort operation described belowin conjunction with FIGS. 10A-10F.

As will be described in further detail below, data fragments includingcolumn files and data traversal programs can be generated and executedas data is processed through a pipeline. The data fragments are used torepresent the cumulative results at various stages of the pipeline(e.g., the result of having performed a subset of the sequenced datapreparation operations). The fragments representing the transformationresults can be cached at various stages of the pipeline for reuse. Forexample, for a given piece of work that was operated on, the cumulativeresults (or representation of the results) of operations on the piece ofwork up to a particular stage in the pipeline can be saved to disk orstored to a cache layer. The cached representation can be later used toreconstruct the state of the data as of the particular stage in thesequence of operations. The data fragments/representation can be cachednot only at the end of the pipeline, but in the middle as well. Thisallows for intermediary results at the various stages of a pipeline tobe viewed. Further, edits to the sequenced set of data preparationoperations defined in a script (e.g., using an editor interface providedby user interface engine 202 of FIG. 2) can reuse the same cached resultwithout having to perform re-computation of the sequenced set of stepsthat led to the cached result. For example, in some embodiments, thecached representation is identified using a signature that is a function(e.g., hash function such as SHA hash function) of the (e.g., string)description of the sequenced set of operations that led to the resultsrepresented by the cached representation. When new data preparationscripts are received (e.g., as a user configures data preparation via aneditor interface), signatures can be generated from the operations ofthe new script and used to determine whether there is an existing cachedrepresentation that can be leveraged.

In some embodiments, the cached representation described herein isoptimized for columnar workloads. The columnar workloads include datapreparation operations that are used to perform columnar datatransformations. In some embodiments, the data formats and structuresused to generate cached representations are also optimized for speed andefficiency, for example, to limit the flow of data throughout a pipelineserver so that as little data as is necessary is worked on as quickly aspossible.

(Re)use of the columnar workload-optimized cache, including thegeneration and reuse of data traversal programs, will be described belowin conjunction with various example data preparation operations. Whileexample details of several data preparation operations are provided forillustrative purposes, the list is not exhaustive, and the techniquesdescribed herein can be adapted accordingly for any other datapreparation operations as appropriate.

Data Preparation Operation Examples

Suppose that a user has specified a data set and a set of sequenced datapreparation operations to perform on the data set via a user interface(e.g., provided by user interface engine 202 of front end 200 of FIG.2), resulting in the script shown in FIG. 6A being generated (e.g.,using script generator 204 of FIG. 2). The script is received by apipeline server (e.g., pipeline server 300 of FIG. 3 from front end 200of FIG. 2), implemented using a distributed computing platform such asApache Spark.

FIG. 6A illustrates an example embodiment of a script. As shown, script600 includes a description of the data set (referred to as “DS1” in thisexample) to be worked on (and imported) at 602. The contents of the dataset to be processed are shown in conjunction with FIG. 6B. The scriptalso includes a set of sequenced operations to perform on the data set.In this example, the set of sequenced operations includes an uppercaseoperation on column A of the data set (604) and a filter operation oncolumn B of the data set (606) on the values “e” and “h.” The sequencedset of operations forms a pipeline through which the data set will beprocessed. In this example, the logical sequence of the operations isalso the physical execution sequence, but need not be (e.g., thephysical execution sequence may be different, for example, in thepresence of a smart optimization compiler). For example, suppose that asequence of data preparation operations includes two operations, “f” and“g,” in successive positions, in that order. A smart compiler maydetermine that performing “g” before “f” would result in exactly thesame result, and would be faster to compute. For instance, in theexample operations specified in script 600, the final result could alsobe obtained by swapping the uppercase and filter steps. Doing so wouldresult in the uppercase operation being performed on far fewer rows,increasing the speed (and efficiency) of the computation.

As shown in this example, the data preparation operations are columnarin nature, where an operation to be performed on a data set is definedwith respect to a particular column. For example, the uppercaseoperation is performed on column “A” of the data set, and the filteroperation is performed based on particular values found in a specificcolumn (column “B”). For such data preparation operations, how an entiredata set is transformed is based on how particular columns are affectedby an operation, or based on the characteristics of the particularcolumns implicated in an operation. This will be leveraged to providetechniques for optimized and efficient performance of data preparationoperations, as will be described in further detail below.

At 608, the script indicates how the results of the data preparationoperations are to be outputted. In this example, the results are to beviewed (e.g., presented to a user in a user interface provided by userinterface engine 202 of FIG. 2). Another example of an option foroutputting results is to publish the results (e.g., export them toanother file).

FIG. 6B illustrates an example embodiment of a data set to be processed.In this example, data set 650 corresponds to the data set specified at602 of script 600 of FIG. 6A.

The processing performed at each stage of the pipeline formed by the setof sequenced operations defined in script 600 will be described infurther detail below. For illustrative purposes, the files written as ofeach step in the sequenced operations are saved (cached), but need notbe.

Import/Start

The first operation of script 600 is Import/Start. After the decision onhow rows should be divided and distributed is made (e.g., by datapartitioning engine 208 of FIG. 2), the data assigned to the variouspartitions is imported. In some embodiments, importing the data includespreparing the data such that it can be quickly accessed sequentially(e.g., read a column of data quickly from top to bottom).

FIG. 7A illustrates an example embodiment of data structures generatedduring an import operation. In some embodiments, the example of FIG. 7Acontinues from the example of FIG. 6B. In some embodiments, the databeing imported in FIG. 7A is the data from data set 650 (DS1) of FIG.6B.

Suppose in this example that DS1 has been split into two logicalpartitions, partition zero (702) and partition one (704). The partitionsare each processed by one or more workers (e.g., Spark workers/pipelineexecutors, as described above). As described above, each partitionincludes a subset of the rows of DS1, and collectively the twopartitions comprise the entire data set. The subsets of rows among thepartitions are non-overlapping and are contiguous.

With the work (data) having been partitioned, each row of DS1 isuniquely identified by a set of coordinates. In some embodiments, thecoordinates indicate the partition in which the row can be found, and anidentifier of the row within the partition. In the examples describedherein, the coordinates are organized as follows: (partition number, rowidentifier). An example of the unique row identifiers is shown inreferences tables 706 and 708, which correspond to partitions zero andone, respectively.

As shown, data set DS1 has been equally divided into two partitions,with the top three rows of the data set assigned to partition zero, andthe bottom three rows assigned to partition one.

In this example, each partition stores the data into sets of filescorresponding to the columns, as shown at 710 and 712. For example, at710, separate column files corresponding to the columns “A,” “B,” and“C,” respectively, of data set DS1 are written (e.g., the contents ofthe data set DS1 are obtained from their source (specified in a script)and re-written into the column files). Each separate column sequentiallydescribes the cells for all of the rows of DS1 that are in thepartition. In some embodiments, the column values that are written areread from the source of the input data set (as specified in a script),and the original source data set is not modified (e.g., the values ofthe source data set are copied into the column files).

Accompanying column files 710 and 712 are lookup tables 714 and 716,respectively. Each row of the lookup table includes a row identifier(“Row_ID”) and indices into the column files (indicating the location ofthe data values for an identified row). In this example, the indicesshown in the index columns are byte indices into their respective columnfiles.

The structure of the lookup table and the column files are optimized forsequential access such that, for example, all of the data can be readdown a column quickly. The structures shown also allow for efficientnon-sequential row probes (e.g., random access probing of a row). Forexample, to access a specific value in a row of a column, a lookup ofthe table can be performed by using a row identifier of the row ofinterest and the column of interest. The index value corresponding tothat (row, column) coordinate is obtained from the lookup table and usedto access the corresponding column file. The value at the index of thecolumn file can then be retrieved directly, without requiring other datanot of interest to be loaded and read.

In this example, the values in the column file are stored sequentiallyand are indexed by byte order. As the values can be of different types(e.g., char, int, etc.) and can be of different sizes (e.g., in bytes),the indices in the lookup table indicate the location of a cell in acolumn file by its starting byte location in the file. For purposes ofillustration, throughout this and other examples described herein,assume that a character has a size of one byte. The numeric values shownin the examples described herein are, also for illustrative purposes,integers with a size of two bytes.

Take for example the column file (718) corresponding to column “C”written by partition one as part of the import operation. The columnfile includes the values ‘cats,’ ‘n,’ and ‘q.’ The corresponding byteindices for the column file are shown at 720 of lookup table 716. Thestarting byte in the “C_file” for the value ‘cats’ is 0, as it is theinitial data value written in the column file. The starting byte in the“C_file” for the value ‘n’ is 4. This is because the value ‘cats,’ whichis a word including 4 characters, has a size of 4 bytes. Thus, thezeroth byte in column file 718 includes the value for the first row ofthe “C” column file (in partition one), the fourth byte starts thesecond row, and the fifth byte starts the third row of the column. Thus,data can be read from the column files by byte index.

By using byte (or any other appropriate data unit of size) indexes, thecolumn values can be tightly packed into a column file, withoutspaces/gaps between values. This allows for space efficient-storage ofcolumn values as well as efficient lookup of those values. As the columnfiles are stored separately and compactly, if an operation requiresoperating on an entire particular column, the corresponding column filecan be read directly (e.g., without indexing) and without reading valuesfrom any other columns that are not of interest. Thus, the datastructures/formats shown are space-efficient, columnar, and optimizedfor specific column operations. As described above, the data formatshown is optimized for both random and sequential access.

In some embodiments, the set of column files and corresponding lookuptable are included together into a file set. In this example, lookuptable 714 and column files 710 are included in file set 722. Lookuptable 716 and column files 712 are included in file set 724. Each fileset is associated with a file name/cache identifier, which can be usedto locate the file set including the actual column values. In thisexample, the file set name/identifier is generated based on the name ofthe step that resulted in the column files being written, and thepartition that wrote the file. For example, the file set 722 written bypartition zero is called “import_ds1_p0,” indicating that the file setwas written by partition zero (“p0”) for the step of importing ds1(“import_ds1”). Similarly, the file set 724 written by partition one iscalled “import_ds1_p1,” indicating that the file set was written bypartition one (“p1”) for the step of importing ds1 (“import_ds1”). Whengenerating the file sets for an operation that is performed across allof the partitions, the handle/cache id that is generated is consistentacross all of the partitions. In this example, for partitions zero andone participating in the import DS1 operation, the handle of the filesets (“import_ds1”) written by the partitions is consistent across bothpartitions, with the difference being the partition number that isconcatenated to the end of the file set name. In some embodiments, thefile sets are written to a cache/storage and can be obtained using theidentifiers described above. The use of such cache identifiers/file setnames will be described in further detail below.

While a data set may have been divided across multiple partitions, asshown, the processing performed with respect to only one partition isshown for the remaining steps of script 600, as the specified set ofsequenced operations do not require movement of information betweenpartitions (i.e., rows will not move between partitions). Similarprocessing is performed in the other logical partition(s) into which theinput data set has been divided. Examples of operations that result intransfer of rows between partitions will be described in further detailbelow.

In addition to the file sets that are written, each partition isassociated with what is referred to herein as a “data traversal program”(DTP). The data traversal program includes a references table and areference stack, which together provide information for how to read thestate of a portion of the data as of a certain stage of a pipeline(e.g., how to read what is the cumulative result of having performedsome portion of the sequenced set of operations on the input data set).A references table includes references of row transformations during aset of sequenced operations, and a reference stack includes a record ofthe sequenced operations and columns that are changed by the sequencedoperations. In some embodiments, as each operation in a sequenced set ofoperations is performed, the references table and the reference stack ofthe data traversal program for the partition are updated to reflect thecumulative transformation result after having performed the sequencedset of operations up to a given operation. In some embodiments, the datatraversal program is stored in a cache layer. This allows the datatraversal program to be quickly accessed and updated as operations areperformed, thereby allowing efficient access of the results of theoperations (including intermediate results) without having to repeat theoperations.

In some embodiments, a data traversal program of a partition, whenexecuted, uses the references table and reference stack of the partitionto obtain a sequenced set of rows that are a subset of the data setresulting from a sequenced set of operations having been performed on aninput data set. The position of the sequenced subset of rows in theentire resulting data set is based on the position of the correspondingpartition in the sequence of partitions. For example, the sequencedsubset of rows obtained from the data traversal program for partition“N” is immediately followed by the sequenced subset of rows obtainedfrom the data traversal program for partition “N+1.” The sequencedsubsets of rows from the various partitions are non-overlapping. Thesequenced subsets of rows, when read in this order, collectively formthe results of a sequenced set of data preparation operations performedon one or more input sets of data.

In some embodiments, the references table and the reference stack of thedata traversal program are updated as each data preparation operation isperformed to reflect the cumulative result of having performed thesequenced set of operations up to a given point in the pipeline. As thepipeline includes various stages and intermediary results, which, forexample, a user may wish to revisit, in some embodiments, a copy of thedata traversal program can be cached at a save point (e.g., before it isupdated by the next step in the sequence of data preparationoperations). The caching allows, for example, incremental saving of thedata that is changing as the data progresses through various points ofthe pipeline/sequenced set of operations.

As shown in the example of FIG. 7A, partitions zero and one are eachassociated with their own data traversal programs, 726 and 728,respectively. Data traversal program 726 associated with partition zeroincludes the references table 706 and reference stack 730. Datatraversal program 728 associated with partition one includes referencestable 708 and reference stack 732. In some embodiments, the datatraversal programs (including corresponding references tables andreference stacks) are initialized (created) as a result of the importbeing performed. As will be described in further detail below, in someembodiments, the data traversal program represents a result of a set ofsequenced data preparation operations and indicates how to assemble oneor more affected columns to derive the result.

Reference stack 730 of partition zero is now described. In this example,the first row of reference stack 730 (which currently includes only onerow after the import step) includes cache identifier (“cache id”) 734.The cache identifier projects out the columns “A,” “B,” and “C,” asindicated by the corresponding entry in the row at 736. Cache id 734,when combined with an indicator of the partition (partition 0), willresult in a file name corresponding to file set 722 (“import_ds1_p0”).This indicates the location of the data that was written due to theimport by part 0. The reference stack is used in conjunction with thecorresponding references table to read a sequenced set of rows that is asubset of the overall data set resulting from the import operationhaving been performed.

An example of reading the result of importing DS1 is as follows.Suppose, for example, that a user would like to see the state of thedata set DS1 after it has been operated (which should appear the same,as import does not make modifications to the data set). The files anddata traversal programs shown in FIG. 7A can be used as follows toassemble DS1 (e.g., for viewing) as of the import step.

In order to read the imported data in its proper order, the datatraversal programs of the partitions are executed in the order of thepartitions to which they correspond. Thus, data traversal program 726 ofpartition zero is executed first (the data traversal programs of thepartitions can also be executed in parallel, with the sub-results fromeach data traversal program placed in their correct order as they areobtained).

Data traversal program 726 is executed as follows. References table 706includes three rows. This indicates that the data traversal program(which is associated with partition zero), when executed, will providethe first three rows of the imported data set. The first row of theimported data set is obtained as follows. The value of the first (and asyet, only) column in the first row (738) of references table 706, thecoordinates (0,0), is obtained. This column of the references tablecorresponds to the first (and as yet, only) row in the reference stack.The row includes cache identifier 734 and identifies columns “A,” “B,”and “C” at 736.

The partition number from the obtained coordinates (zero) is appended tocache id 734 to obtain the file name “import_ds1_p0,” which correspondsto file set 722 of the same name. File set 722 is then accessed. The rowidentifier of the obtained coordinates (zero) is then obtained. Theobtained row identifier is used in conjunction with the columns “A,”“B,” and “C” identified at 736 to perform a lookup of lookup table 714of file set 722. As columns “A,” “B,” and “C” have been identified, theobtained row number “zero” is used to look up, using the lookup table,the values in the zeroth row of those columns. The corresponding byteindexes in the zeroth row of the index columns of the lookup table areobtained and used to access the column files 710. Thus, the rowincluding the values “a,” “b,” and “c” for columns “A,” “B,” and “C” isobtained from corresponding column files 710.

The processing performed by the data execution program to arrive at thefirst row of the imported ds1 data set is described again in conjunctionwith FIG. 7B.

FIG. 7B illustrates an example embodiment of executing a data traversalprogram. In the example of FIG. 7B, the various references tables,reference stacks, and file sets described correspond to their respectivecounterparts in FIG. 7A.

The data traversal program (e.g., data traversal program 728 of FIG. 7A)for partition zero is executed. The data traversal program begins byreading the first row (752) of references table 750 (which correspondsto references table 706 of FIG. 7A). The single entry in this rowincludes the coordinates (0,0), which is a reference indicatingpartition zero, row id zero.

As shown, row 752 includes a single column, which is mapped/correspondsto the only row in reference stack 754, row 756. In this example,reference stack 754 corresponds to reference stack 730 of FIG. 7A. Row756 includes two entries, one for a cache identifier. As will be shownbelow, the cache identifier is combined with the partition numberidentified in the coordinates obtained from row 752 to locate a fileset. The second entry in row 756 includes an indication of the columnswhose values are to be obtained using the located file set.

The coordinates obtained from row 752 are shown at 758, and indicate, asshown, a partition number (zero) and a row identifier (zero). Theentries obtained from row 756 of reference stack 754 are shown at 760.The obtained values shown at 758 and 760 are used together as follows.

The partition number “zero” extracted from reference 758 is combinedwith the cache id “import_ds1” value extracted from 760 to generate thefile name “import_ds1_p0” (762). The combination is performed, forexample, by concatenating strings, generating a hash of the combinedvalues, or by any other appropriate combination function. This is usedto locate and access the file set of the same name (file set 722 of FIG.7A), which was written as a result of the import step, as describedabove in conjunction with FIG. 7A.

The row identifier “zero” extracted from reference 758 is then used toperform a lookup of lookup table 766 of file set 722. Based on theextracted row identifier “zero,” row 768 of lookup table 766 isidentified and accessed.

Based on the column titles 770-774 (“A,” “B,” and “C,” respectively)specified in reference stack row 760, the values for those specifiedcolumn titles corresponding to row 768 are looked up and obtained. Thisis performed as follows. Because columns “A,” “B,” and “C,” have beenspecified, the index values for those corresponding columns in row 768are obtained from lookup table 766. Those indices are then used tolookup actual data values written to respective corresponding columnfiles in the file set. In this example, the corresponding values of thespecified column titles “A,” “B,” and “C” are “a,” “b,” and “c.” Thus,the first row of imported ds1 has been read/obtained.

The next two rows of imported ds1 are then read by moving down theentries in the reference table and performing the same process describedabove. For example, the entry in the second row of references table 750(with the reference coordinate (0, 1)) is combined with the first row ofreference stack 754 (based on the mapping of the first and only columnof the references table with the first and only row of the referencesstack) using the data traversal program processing described above toobtain the values “d,” “e,” and “f” from file set 722 The third and lastrow of imported DS1 (including the values “g,” “h,” and “i”) can also besimilarly obtained using the data traversal program of partition zero.

Data traversal program 728 of partition one is then also similarlyexecuted, as described above, to obtain the bottom three rows of DS1, inorder.

The two obtained subsets of sequenced rows are then combined togetherand provided as output. For example, if the user would like to view theresults in a user interface, the sequenced subsets of rows are displayedin corresponding partition order (i.e., the subset of sequenced rowsobtained using the data traversal program of partition one is displayedbelow the subset of sequenced rows obtained using the data traversalprogram of partition zero). If the user indicates that they would liketo publish the results, then the sequenced subsets of rows are appendedto each other based on corresponding partition order (i.e., the subsetof sequenced rows obtained using the data traversal program of partitionone is appended to the bottom of the subset of sequenced rows obtainedusing the data traversal program of partition zero).

In some embodiments, the execution of the data traversal programs isperformed in parallel on each partition. The sequenced subsets of rowsresulting from the data traversal programs are then placed in the orderof the partitions from which they were obtained.

The data traversal programs written as of the import stage (andrepresenting the results of the import operation) can be saved. Thecached data traversal program can be used at a later time, for example,to avoid having to regenerate references and reference tables.

In the above example, the references tables include only one column, andthe reference stack includes only one row. Additional examples involvingreferences tables with multiple columns and/or reference stacks withmultiple rows will be described in further detail below.

Continuing with the example of script 600, example processing involvedin performing the uppercase and filter operations is now described. Asthe uppercase and filter operations do not result in the movement ofrows between partitions, and can thus be performed by the partitionsindependently of each other, the processing that occurs on partitionzero is shown below. Similar processing occurs on partition one.

Uppercase

After importing the data, the next step in script 600's pipeline is toperform an uppercase on the values of column A. Here, the operation isperformed relative to a specific column, column A. FIG. 8A illustratesan example embodiment of an updated data traversal program (810) and newfile set (806) generated as part of performing the uppercase on column Aoperation.

In this example, the uppercase operation on column A is performed asfollows. Prior to performing the uppercase operation, the state of thedata traversal program of partition zero is as shown in the example ofFIG. 7A.

The current values of column A are obtained, for example, by performinga reading of column A using the current state of the data traversalprogram. The uppercase operation is performed on those obtained columnvalues. Because the values of column A are now different as a result ofthe operation, a new column file for the new, uppercase version ofcolumn A is written, as shown at 802 (that includes the uppercasevalues). A corresponding lookup table 804 is also written so that thevalues in the new version of column A can be looked up. The new columnfile 802 and corresponding lookup table 804 are included in file set806, which, in this example, is given the name “Up_A_Import_ds1_p0,” asshown at 808. In this example, the file set name is generated bycombining together (e.g., using a string concatenation, hash function,etc.) the operations that have been performed thus far that resulted inthe column files in the file set having been written. The partitionnumber that wrote the file set is also added to the name. For example,the name “up_A_Import_ds1_p0” at 808 is generated to reflect that fileset 806 was written by partition zero when performing an uppercaseoperation on column A that was performed after importing DS1.

As shown, because only column A has been specified in the operation, andonly the values in column A were modified (i.e., column A is the onlyactive column in this operation), only a file set for the new version ofcolumn A need be created at this stage of the pipeline. Thus, no newdata needs to be generated/written for other columns in the data set DS1that were not touched by the uppercase operation. Thus, the data that ischanging as of the execution of a data preparation operation can bewritten incrementally.

Due to a new column file having been written as a result of theuppercase step, the data traversal program of partition zero isupdated/amended (e.g., from its state as of the import step)accordingly. The new state of the data traversal program as of theuppercase step is shown at 810.

The new data traversal program is generated as follows. The current datatraversal program that partition zero is responsible for is obtained(data traversal program 726 of FIG. 7A as of the import step). A new row812 is added to (“popped onto”) the top of the existing reference stackto produce new reference stack 814 of partition zero. The new row 812indicates: (1) the cache identifier/handle portion of the newly writtenfile set 806 (without partition number); and (2) the title of the column(“A”) that was written. In this example, a new version of the column Afile has been written. This new version of column A supersedes theprevious version of the column A file that was written as part of theimport step. To represent this, the “A” value of row 816 has been markedunavailable to the data traversal program, as indicated by anunderscore. When reading the data, the value from the new column A filewill be read, and the earlier version of the column A file (found infile set 722 of FIG. 7B) will not be accessed and read. This allows thedata traversal program to enforce only the most recent version of acolumn to be read.

A new column 816 is also added to the left of the existing referencestable (which included only column 818), resulting in a new referencestable 820 for partition zero. In this example, the rows of the importeddata set did not change position, and thus each of the coordinates inthe references included in new column 816 still identify the samepartitions and row identifiers as shown in column 818.

The columns in the references table, from left to right, are mapped tocorresponding respective rows in the references table, from top tobottom. For example, column 816 of references table 820 is mapped to row812 of reference stack 814. Column 818 of references table 820 is mappedto row 816 of reference stack 814. This mapping will inform how the datatraversal program as of a particular pipeline stage reads values frompreviously written file sets to assemble rows of a data set as of theparticular pipeline stage. Any other appropriate mapping can beperformed.

Thus, the data traversal program from the import step is updated/amendedto reflect the new result of having performed an uppercase on column Aafter importing ds1. Data traversal program 810 can be cached to storethe representation of the result at the stage in the pipeline at whichds1 has been imported and then column A has been uppercased. In someembodiments, a signature corresponding to the data traversal program isgenerated. The signature can be generated based on the operations thatled to the result represented by the data traversal program to be cached(e.g., by hashing the representations of the operations (e.g., stringrepresentations) together, by concatenating the operations together, orthrough any other combination function). A copy of data traversalprogram 810 is then cached with its corresponding signature. The cacheddata traversal program can then be later identified by its correspondingsignature, as will be described in further detail below.

An example of executing the updated data traversal program 810 to obtaina portion of the results after having performed the uppercase on columnA after importing DS1 is described in conjunction with FIG. 8B.

FIG. 8B illustrates an example embodiment of executing a data traversalprogram. In the example shown, a first row of the data set that resultsfrom performing an uppercase on column A after importing data set DS1 isread. The row can be read, for example, when the results of the importand then the uppercase operations are to be outputted (e.g., for viewingin a user interface, for publishing/exporting, etc.). In the example ofFIG. 8B, the various references tables, reference stacks, and file setscorrespond to their respective counterparts in FIG. 8A.

In this example, the data traversal program (e.g., data traversalprogram 810 of FIG. 8A) for partition zero is executed. The datatraversal program begins by reading the first row 852 of referencestable 850 (which corresponds to references table 820 of FIG. 8A). Therow includes two entries, references/coordinates (0,0) in column 854,and references/coordinates (0,0) in column 856. As described above, theleftmost column (854) of references table 850 is mapped/corresponds tothe topmost row (860) of reference stack 858 (which corresponds toreference stack 814 of FIG. 8A). The rightmost column (856) ofreferences table 850 is mapped/corresponds to the bottom-most row (862)of reference stack 858.

The pairing of the reference (0,0) at row 852 and column 854 ofreferences table 850 with the entries in row 860 of reference stack 858is shown at 864. The pairing of the reference (0,0) at row 852 andcolumn 856 of references table 850 with the entries in row 862 ofreference stack 858 is shown at 866.

The processing performed by the data traversal program using pairing 864is described first (the processing of 864 and 866 may be performed inany order, in parallel, or in any other appropriate manner). Thecoordinates obtained from row 852 and column 854 of references table 850are shown at 868, and indicate as shown a partition number (zero) and arow identifier (zero). The entries obtained from row 860 of referencestack 858 are shown at 870. The obtained values shown at 868 and 870 areused together as follows.

The partition number “zero” extracted from reference 868 is combinedwith the cache identifier “Up_A_Import_ds1” value extracted from 870 togenerate the file name “Up_A_Import_ds1_p0” (872). The combination isused to locate and access the file set of the same name (file set 874),which was written as a result of the uppercase on column A operationbeing performed on imported DS1, as described above in conjunction withFIG. 8A. In this example, file set 874 corresponds to file set 806 ofFIG. 8A.

The row identifier “zero” extracted from reference 868 is then used toperform a lookup of lookup table 876 of file set 874. Based on theextracted row identifier “zero,” row 878 of lookup table 876 isidentified and accessed.

Based on the column title 880 (“A”) specified in reference stack row870, the value for the specified column title corresponding to row 878is obtained. The value is obtained by looking up the index value forcolumn A in row 878 of the lookup table. This provides the byte index“0.” The value at the zeroth byte index of the file for column A(A_file) is obtained. This is the value “A.” This is the uppercaseversion of the value prior to the uppercase step (“a”). Thus, the valuefor the column A in the first row of the data set resulting from theuppercase on column A of the imported data set DS1 is obtained.

The data traversal program is then configured to use pairing 866 toobtain the remaining values for columns B and C. In contrast to theprocessing described above in which the current value (as of stage ofpipeline after the uppercase on A after import ds1) for column A wasobtained from the file set “Up_A_Import_ds1_p0,” the current values forcolumns B and C are obtained from a different file set. In this example,the values for columns B and C are obtained using the file set that waswritten during the import step (“Import_ds1_p0”). This reflects, inpart, that columns B and C were not changed by the uppercase on thecolumn A operation, and thus, their values written at the previous stageare still valid (and are still the most current version) at this stageof the pipeline.

Pairing 866 is used by the data traversal program as follows. Thecoordinates obtained from row 852 and column 856 of references table 850are shown at 882, and indicate as shown a partition number (zero) and arow identifier (zero). The entries obtained from row 862 of thereference stack are shown at 884. The obtained values shown at 882 and884 are used together as follows.

The partition number “zero” extracted from reference 882 is combinedwith the cache id “import_ds1” value extracted from 884 to generate thefile name “import_ds1_p0” (886). The combination is performed, forexample, by concatenating strings, generating a hash of the combinedvalues, or by any other appropriate combination function. This is usedto locate and access the file set of the same name (file set 888), whichwas previously written as a result of the import step, as describedabove in conjunction with FIG. 7A. In this example, file set 888corresponds to file set 722 of FIG. 7A.

Based on the column titles 890 and 892 (“B” and “C,” respectively)specified in reference stack row 884, the values for those specifiedcolumn titles corresponding to row 894 are looked up in file set 888 andobtained. This is performed as follows. Because columns “B” and “C” havebeen specified, the byte index values for those corresponding columns inrow 894 are obtained. Those indices are then used to look up actual datavalues written to respective corresponding column files in the file set.In this example, the corresponding values of the specified column titles“B” and “C” are “b” and “c,” respectively.

In this example, as described above, because the column A was modifiedby the uppercase operation, the column title “A” has been removed(indicated by an underscored) from row 862 of reference stack 858 toindicate that the version of column A that is obtained from file set 888is no longer valid/current and values should not be obtained from thatversion of the column A file. Thus, the value for column A in file set888 was not obtained.

As shown above, new column files (and corresponding lookup tables) areonly written for columns that are changed by an operation. The referencestack is used in part to indicate where the most current (as of somecorresponding stage of a pipeline) version of a column is located (i.e.,the location of a file set and what columns should be read from thatfile set).

The values obtained from the two file sets are combined together toproduce the first row of the cumulative result of performing anuppercase on column A after importing data set DS1 (“A,” “b,” “c”).

The remaining rows of the result are determined by going down the rowsof the references table in order and performing the same processing asdescribed above. By executing the data traversal program on thereferences table in this order, the subset of the overall results thatare obtained using the data traversal program for partition zero will bein their correct order.

Similar processing is performed on partition one. The sub-resultsobtained for partition zero and partition one are then combined togetherto form the overall result, where the subset of results obtained frompartition zero precede the subset of results from partition one.

As shown in this example, two different file sets were accessed todetermine the values that make up a single row in a data set resultingfrom multiple operations having been performed on an input data set.

Filter

Continuing with the example of script 600 of FIG. 6A, after performingan uppercase on column A, the next stage of the pipeline/next step inthe set of sequenced operations is to filter on column B. In particular,the data is filtered on column B according to attached criteria, namelythat the data is to be filtered on the values “e” and “h” in column B.This will potentially reduce the total number of rows in the data set(and the number of rows in each partition).

In the filter operation, no data values are modified. Thus, because nocolumns are modified, no new file sets are written as a result of theoperation. However, the number of rows represented by the data traversalprogram of a partition may be decreased. Thus, the references table andreference stack of a partition will be updated to reflect this.

In one example embodiment, the state of the data traversal program (andreferences table and reference stack) is determined/updated as describedbelow in conjunction with FIG. 9A.

FIG. 9A illustrates an embodiment of a process for updating a datatraversal program to reflect the results of a filter operation. In someembodiments, the processing performed in FIG. 9A is performed by one ormore pipeline executors (e.g., Spark workers) working on a partitionsuch as partition zero. In some embodiments, each executor operates onits work portion independently (as rows will not move between partitionsas a result of the filter operation).

The references table is updated as follows. At step 1 (902), the currentreferences (as of the uppercase on column A having been performed) forthe partition are obtained. In some embodiments, obtained references areobtained from references table 820 of FIG. 8A. Each row of references intable 904 represents a particular row in the cumulative results ofhaving performed the sequenced set of operations up to the uppercase oncolumn A operation.

At step 2 (906), the column B values corresponding to the rowsrepresented by table 904 are obtained. In some embodiments, the valuesare obtained by performing a data traversal using the references andcorresponding reference stack as described above. In some embodiments,the corresponding reference stack that is used to obtain the values isreference stack 814 of FIG. 8A. In some embodiments, a column populatedusing the column B values is added to the right of table 904 to generatemodified table 918.

At step 3 (908), table 918 is filtered according to the filter criteria(filter on column B values “e” and “h”). The results of the filter areshown at 910. For example, in a Spark implementation, the Spark filteroperation is called on table 918 (represented as an RDD). The filtertransformation returns a new RDD with a subset of the rows in table 918,which is shown at 910. At step 4 (912), the column B values are dropped,resulting in table 914 that includes only references. These referencesrepresent the rows that remain after the filtering operation. At step 5(916), table 914 is saved as the updated references table for this stageof the pipeline.

Regarding the reference stack, because no new column data has beenwritten, the reference stack need not be updated for the filter step. Insome embodiments, a save is automatically performed after a filter,which includes saving the current references table. When performing thesave, in some embodiments, a new entry (row) is popped onto the top ofthe reference stack. In some embodiments, the new row of the referencestack includes a handle/cache identifier to the saved references tableso that it can be retrieved for later use. For example, in someembodiments, the references table is stored as part of a file set thatis referenced in part using the handle/cache identifier. In thisexample, the file set would include only the references table, but nolookup table and column files (as no new column data has been written).The columns portion of the new row of the reference stack is empty. Acorresponding column in the references table is also generated.

This results in the data traversal program shown in FIG. 9B.

FIG. 9B illustrates an example embodiment of a data traversal program.In this example, an updated data traversal program for partition zerorepresenting the result of having done the filter operation on column Bon the values “e” and “h” is shown. The data traversal program includesupdated references table 952, which was, for example, generated usingthe processing described in FIG. 9A. As described above, because a savewas performed after the operation, even though no data has beenmodified, the reference stack 954 has been updated from the previousstage of the pipeline.

To read the cumulative results at this stage of the pipeline, the datatraversal program for partition zero (and other logical partitions) isexecuted in a similar manner as described above. For example, the datatraversal program shown in FIG. 9B can be executed to obtain a subset ofthe cumulative results (the first two rows of the cumulative results) ofperforming the filter operation after the uppercase operation after theimport operation. In some embodiments, if there are no columns specifiedin a row of reference stack entries, then no data values are read (i.e.,only the reference stack entries with columns relevant to the datatraversal program are read). Thus, by executing the data traversalprogram shown in FIG. 9B, the results shown at 956 are obtained.

As shown, the result of cumulative operations is reflected in the datatraversal program, but there is not necessarily any indication in thedata traversal program of what exact operations were performed toachieve those cumulative results. In some embodiments, when caching thedata traversal program of a particular stage in a pipeline, a set of oneor more signatures is built/generated based on the steps that wereperformed to achieve the cumulative result. The one or more generatedsignatures are assigned to the cached data traversal program.

As shown, the processing that was performed to arrive at the state ofthe data as of a filter operation was to look directly at the values ofcolumn B and filter those values to determine what rows remain in thedata set. Only those rows that remained are reflected in the updatedreferences table as of the filter step. No new data was written whenperforming the filtering using this data representation. Rather, thereduction in rows as a result of the filter is captured in the reducednumber of rows in the references table, and was accomplished by lookingonly at the values of column B. This is in contrast to other filteringtechniques that write out the results, where the cost of writing anentire filtered data set is a function of the total number of columns ofthe data set. Here, a compact representation of the results is updatedto reflect the cumulative results of a sequenced set of data preparationoperations.

The example operations described above with respect to the script ofFIG. 6A would not result in movement of information between partitions.In the following example, an operation (sort) which results in movementof references across partitions (e.g., where rows exchange partitions)is shown.

Sort

FIG. 10A is a diagram illustrating an embodiment of a data set to besorted. Throughout this example sort operation, the data set to besorted (1000) is referred to as “DS.” Data set 1000 includes twocolumns, C0 and C1, and four rows.

FIG. 10B is a diagram illustrating an embodiment of data traversalprograms and file sets. Continuing with the example of FIG. 10A, supposethat data set DS has been divided into two partitions, partition zeroand partition one, each with two rows, and imported, as shown at 1010and 1016. In this example, partition zero has initialized data traversalprogram 1012 and written file set 1014. In this example, file set 1014is named “import_ds_p0.” Similarly, partition one has initialized datatraversal program 1018 and written file set 1020. In this example, fileset 1020 is named “import_dsp1.” The cache identifiers for partitionzero's reference stack and partition one's reference stack both includethe same cache identifier/handle, “Import_ds.” In some embodiments, eachpartition stores its respective written file set local to the place ofits computation.

In this example, the sort condition C0 is used to determine where therows of the data set should move. In some embodiments, a distributedcomputing platform such as Spark is leveraged to perform the work ofmoving rows (represented by references) to the correct place (i.e., themovement of rows due to the sort is represented by moving referencesbetween partitions).

In this example, the sort is to be performed on C0. FIG. 10C illustratesan example of a sorted result. Data set DS prior to the sort is shown at1030. The result of the sort operation on data set DS is shown at 1032.As shown, rows 1034 and 1036 of the data set DS swap positions due tothe sort operation. The process involved in updating data traversalprograms to represent the result of the sort operation will be describedin further detail below.

FIG. 10D is a diagram illustrating an embodiment of a process forperforming a sort operation. In this example, the sort operation will beimplemented in part by generating and sorting key-value pairs. Akey-value pair allows for data to be represented as a value and some keythat characterizes that value. In the following example, the key will bewhat is sorted on. As will be shown in this example, key-value pairswill be generated, wherein the value of the key-value pair is a row(represented by a set of references) and the key is the actual datavalue of C0 for that row. The key-to-row pairs will then be sorted bykey, which will cause the rows (references) to be rearranged (e.g.,across the partitions). One embodiment of the sort operation processingis performed as follows. As will be shown below, the result of theprocessing will be an updated references table for an updated datatraversal program that represents the result of the sort operation onthe imported data set DS.

At step 1 (1040), all rows of the data set DS are obtained. Each row ofthe data set DS is represented using a set of one or more references,which are obtained from data traversal programs 1012 and 1018 of FIG.10B. In this example, the references above line 1042 were obtained fromdata traversal program 1012 of partition zero. The references below line1042 were obtained from data traversal program 1018 of partition one. Insome embodiments, the references shown at step 1 are the referencestable for each partition.

At step 2 (1044), C0 values for each row are populated. As will be shownbelow, the C0 values will be used as keys for each row. A sort will thenbe performed on the keys. In some embodiments, the C0 values for eachrow are obtained by executing data traversal programs 1012 and 1018 ofFIG. 10B to look up C0 values from respective file sets in the mannerdescribed above.

At step 3 (1046) keys on C0 are generated. In this step, the obtained C0values are used as keys that are paired with their corresponding rows(references) to generate key-to-row pairs. In some embodiments, at step3, the values that were obtained at step 2 are extracted to the keyposition. In some embodiments, step 3 is an intermediate step togenerating a key-to-row, key-value pair. At step 4 (1048), the valuesobtained at step 2 are dropped from the rows. This results in a set offour key-value pairs as shown at 1050.

In some embodiments, the key-value pairs are generated by manipulatingthe reference tables in place. First, the references tables areobtained, as described in step 1. The C0 values are pulled/extractedfrom file sets at step 2 and added as additional cells of the referencestable (e.g., in a new column added to the right of the referencestable). The C0 values are copied to create the key-value pair by copyingthe C0 values to the left of the references table (as the left positioncorresponds to the “key” position of the key-value pair). The extractedvalues that were in the cells to the right of the references table aredropped to save storage space. The key-value pairs are also referred toherein as “key-to-row pairs.”

In some embodiments, the key-value pair generation is performed inparallel, by various partitions/workers, as they stream in rows fromfile sets and obtain corresponding C0 values to be used as keys.

At step 5 (1052), the key-to-row pairs 1050 generated at step 4 aresorted by key (e.g., by issuing the Spark “sortByKey” command on thekey-to-row pairs). The result of the “sortByKey” command is shown at1054, where the key-value pairs have been sorted by the key values(i.e., C0 values). As shown, the position of key-to-row pair 1056 andkey-to-row pair 1058 have been swapped due to the “sortByKey” command.

At step 6 (1060), the keys of 1054 are removed so that only referencesremain. As the keys were added to form key-value pairs for sortingpurposes, they are no longer needed and are removed. After removal ofthe keys, only references 1062 remain. In this example, because a savepoint is to be created after the sort operation, at step 6, a referencecheckpoint is also created (where, in some embodiments, each savecreates a reference checkpoint). In some embodiments, creating thereference checkpoint includes, as with the filter operation describedabove, updating and saving the references tables. As with the filteroperation, a new column of references is added (shown at 1068). In thisexample, column 1068 is added to the left of column 1062. The newentries in column 1068 are assigned reference values based on theupdated partition/row identifier of their corresponding references incolumn 1062. For example, the top two references in column 1062 (aboveline 1066) will be associated with partition zero. Thus, the top twocorresponding values in column 1068 above line 1066 will be (0,0) and(0,1). Similarly, the bottom two references in column 1062 will beassociated with partition one. Thus, the bottom two corresponding valuesin column 1068 below line 1066 will be (1,0) and (1,1). If no save wereto be performed after the sort operation, then column 1068 would notneed to be added.

In some embodiments, as part of creating the reference checkpoint(because the references table is to be saved), a new row is added to thetop of the corresponding reference stacks, as in the filter operationdescribed above. For example, the new row in a references stack includesa handle/cache identifier to the corresponding saved references table,while the columns portion of the row is left empty. This newly added rowof the reference stack corresponds to the new column that was added tothe references table. In some embodiments, if no save were to beperformed after the sort operation, then the new rows would not need tobe added to the reference stacks.

Examples of the updated references table and reference stacks are shownin conjunction with FIG. 10E.

At step 7 (1064), the references are saved. In this example, thereferences above line 1066 are saved as the newly updated referencetable for partition zero. The references below line 1066 are saved asthe newly updated reference table for partition one.

In one example implementation, steps 1-7 are implemented/performed asfollows. Partitions zero and one separately and in parallel performsteps 1-4. In some embodiments, a partition performs steps 1-4 to obtainone key-value pair at a time (i.e., serially). As the key-value pairsare generated by the partitions, which operate in parallel, they arestreamed by the partitions to a collector (e.g., Spark collector). Forexample, the collector is provided, by each partition, an iterator,which the collector uses to read one key-value pair at a time (i.e., byasking the iterator “next” to obtain the next key-value pair (if itexists)). The collector then sorts the key-value pairs as it receivesthem from the various iterators. Upon completion of the sort, thecollector itself returns an iterator, from which the sorted key-valuepairs can be streamed serially. The sorted key-value pairs are streamedto their appropriate partitions. This allows the references to bedistributed to their appropriate partitions. In some embodiments, aglobal sort is performed. Key-value pairs are then sent to theirappropriate partitions. A local sort is then performed inside apartition to ensure that the key-value pairs are in the correct order.

FIG. 10E illustrates an example embodiment of data traversal programs.In this example, the data traversal programs updated as of the sort onthe C0 operation are shown (using the processing of FIG. 10D describedabove). The data traversal program for partition zero is shown at 1070.The references table for data traversal program 1070 was generated usingthe references above line 1066 of step 6 (1060) of FIG. 10D. The datatraversal program for partition one is shown at 1072. The referencestable for data traversal program 1072 was generated using the referencesbelow line 1066 of step 6 (1060) of FIG. 10D.

In this example, as with the filter operation, no new data (columns) waswritten after the sort. However, because the results of the sortoperation are saved, and a reference checkpoint created in step 6 above,a new entry/row has been popped onto the top of the reference stacks, asshown at 1074 and 1076. No columns were written, so the column portionsof the new rows are empty. If no save were done, then the referencestacks for each partition would remain the same.

As shown in this example, as a result of the sort operation processingdescribed above, the references (1,0) and (0,1) have exchangedpartitions. Although the data traversal program for a partition includesreferences in its references table that were from two partitions,execution of the data traversal programs to read the subset of resultsmaintained by those data traversal programs is performed in the samemanner as described above.

For example, as the references table for a single partition includes tworows from different partitions, the values for those rows must beobtained from two different file sets (e.g., file sets 1014 and 1020 ofFIG. 10B). However, there is only one cache identifier in the referencestack for the partition. By executing the data traversal program in themanner described in the examples of above, both file sets can beaccessed. This is due in part to the names of file sets 1014 and 1020sharing the same base/handle, “import ds.” Thus, when executing the datatraversal program, the appropriate file set will be obtained bycombining the partition identifier of the reference/coordinates beingevaluated to the base/handle “import ds” cache identifier from thereference stack. In some embodiments, the file sets are stored locallyto the partition that wrote them. When a row exchanges partitions, insome embodiments, its corresponding file set is replicated locally onthe node to which the row has moved. This allows the file sets to belocally accessible, improving speed in obtaining values, as well asreducing network bandwidth (e.g., in transferring data between nodes).In other embodiments, the file set is not replicated, and is referenced.

As shown in the above example sort processing, portions of the sortoperation are performed in place, such as the generation of key-valuepairs which will be sorted by key. This provides memory optimization,where a new memory space does not to be created to store key-valuemappings. Rather, existing data entities are modified until they are ina format that is able to be sorted. Additionally, the only values thatwere read from the file sets were C0 values. The movement of the rows ofthe data set, represented by the references, was determined based on thesorting of just the C0 values. References were then moved to differentpartitions to create updated data traversal programs that reflect theresult of the sort.

This is in contrast to the manner in which sort operations are handlednatively in computing platforms such as Spark. For example, in Spark,actual data is moved and written, which involves a greater amount ofdata than writing references as described above, and is therefore morecostly.

FIG. 10F illustrates an example embodiment of a native Spark sort.Suppose in this example, that at start 1080, a data set 1082 has beendivided into two partitions by Spark, as indicated by dividing line1084. In this example, each row in the data set may have a large numberof values, all of which will be operated on by Spark. This is incontrast to the techniques described herein, where referencesrepresenting the rows of the data set are manipulated, rather thanperforming operations on entire sets of actual data. At 1086, keying byC0 values is performed to generate key-value pairs. At 1088, thekey-value pairs are sorted by key. The keys are then dropped at 1090 toobtain the resulting data set. As shown in this example, the operationstarts with all of the data of the entire data set, which is carriedthroughout the operation. This results in a potentially largeconsumption of resources, such as central processing unit (CPU)resources, memory resources, disk resources, bandwidth (e.g., to moveentire data sets between partitions), etc. in order to accommodate theentire data set. Using the techniques described herein, rather thanoperating on actual data sets, a compact representation of the data set(e.g., data traversal program) is operated on, and data values areobtained only as necessary. This allows for a much smaller amount ofdata to be processed through a pipeline of sequenced operations,improving the efficiency of performing data preparation.

In the above, operations with respect to a single data set wereperformed. In the following example data preparation operations ofappend and join, multiple data sets are combined. The data sets beforecombining could have each potentially been processed through their ownpipelines before being combined. As will be shown below, the resultingdata traversal programs for the combined data sets will comprisepartitions with multiple histories of what has happened to them.

Append

FIG. 11A illustrates an example embodiment of a script including anappend operation. At 1102, the location of a first data set (referred toas “DS1” in these examples) to be imported is specified. At 1104, thelocation of a second data set (referred to as “DS2” in these examples)to be imported is specified. At 1106, the append operation is specified.As part of specifying the append operation, one of the data sets to beappended is designated as the driving (anchor) table, to which the othertable will be appended (referred to as the “append table”). In thisexample, DS1 is the driving table, and DS2 is the append table. Inexample script 1100 a specification of what columns in DS1 and DS2 toappend on is also shown. In this example, column C00 of DS1 is mapped tocolumn C01 of DS2. Column C10 of DS1 is mapped to column C11 of DS2. Theexample data sets DS1 and DS2 and the resulting appended data set basedon the conditions specified in script 1100 are described in conjunctionwith FIG. 11B.

FIG. 11B illustrates an example embodiment of data sets to be appended.In this example, data set DS1 is shown at 1110. Data set DS2 is shown at1112. The resulting appended data set is shown at 1114. As shown, as DS1has been designated as the driving table according to script 1100 ofFIG. 11A, DS2 has been appended to the bottom of DS1, where column C01of DS2 has been appended to column C00 of DS1, and column C11 of DS2 hasbeen appended to column C10 of DS1, the mapping of which was describedin script 1100 of FIG. 11A. Also shown is a renaming of the columns forthe appended data set. For example, the new column that includes columnC01 of DS2 appended to column C00 of DS1 has been renamed to column“C0.” Similarly, the new column that includes column C11 of DS2 appendedto column C10 of DS1 has been renamed to column “C1.”

FIG. 11C illustrates an example embodiment of logical file/name spacesassociated with pipelines for two different data sets. Shown in thisfigure are DS1 and DS2, which have been imported prior to the appendoperation. In the example shown, DS1 and DS2 have been imported in theirown respective pipelines (where a pipeline has been declared for DS1 anda separate pipeline has been declared for DS2). In some embodiments,declaring a pipeline includes importing the data set (e.g., as describedabove) and declaring the transformation steps that will be applied tothe data set. In the DS1 pipeline 1120, DS1 has been divided into twopartitions, partitions zero and one, each with two rows of DS1. The datatraversal program for the partitions zero and one are shown at 1122 and1124, respectively. The top two rows of DS1 are represented by datatraversal program 1122 of partition zero, and the bottom two rows of DS1are represented by data traversal program 1124 of partition one. In theDS2 pipeline 1126, DS2 has been divided into three partitions (partitionzero, partition one, and partition two), each including one row of DS2.The data traversal program for the partitions zero, one, and two areshown at 1128, 1130, and 1132, respectively. The top row of DS2 isrepresented by data traversal program 1128 of partition zero, the middlerow of DS2 is represented by data traversal program 1130 of partitionone, and the bottom row of DS2 is represented by data traversal program1132 of partition two. The corresponding file sets written by thepartitions are also shown. In some embodiments, the data sets DS1 andDS2, being in different pipelines, were partitioned independently.

In this example, as independent pipelines have been declared for DS1 andDS2, the numbering for the logical partitions for each pipeline bothstart from zero. In some embodiments, each pipeline is associated withits own name/file space.

FIGS. 11D and 11E illustrate an example embodiment of data traversalprograms before and after the append operation, respectively. Thepartitions and corresponding data traversal programs in the DS1 spaceand DS2 space shown in FIG. 11D correspond to the partitions andcorresponding data traversal programs in the DS1 space and DS2 spaceshown in FIG. 11C.

In some embodiments, appending the two data sets includes creating a newpipeline for the appended result (e.g., a new pipeline is declared forthe new appended data set). The pipeline includes its own file/namespaceand partitions. In this example append, the number of partitions in thenew pipeline equals to the total number of partitions across the twopipelines for the data sets being appended together. For example, if DS1included M partitions, and DS2 included N partitions, the new pipelinewould include M+N partitions. Thus, in this example, as the DS1 pipelineincludes two partitions, and the DS2 pipeline includes three partitions,the resulting pipeline (referred to herein as the “project” pipeline)includes five partitions.

The append operation effectively places the rows of DS2 under the rowsof DS1. As will be shown below, this result is represented by placingall of the partitions of DS1 and DS2 under a single pipeline (the new“project” pipeline). By doing so, the partitions are treated as onesingle data set (rather than two separate data sets, as they were priorto the append). When placing the partitions under the single pipeline,the partitions (which include their corresponding data traversalprograms) are renumbered so that their ordering reflects the newarrangement of rows in the appended data set (i.e., the partitions havebeen remapped from their original pipeline space to the new projectpipeline space). An example of the resulting “project” pipeline space isdescribed in conjunction with FIG. 11E.

FIG. 11E illustrates an example of partitions in a pipelinefile/namespace. In this example, “project” pipeline 1140 was declared aspart of the append operation. Project pipeline 1140 includes fivelogical partitions.

As shown, each partition of the new pipeline corresponds to an existingpartition in the DS1 and DS2 pipeline spaces. In this example, projectpipeline partition zero corresponds to partition zero of the DS1 space.Project partition one corresponds to partition one of the DS1 space.

Because DS2 is appended below DS1, partition zero of DS2 pipeline spacecorresponds to partition two of the new project pipeline space.Partition three of the project pipeline space corresponds to partitionone of the DS2 pipeline space. Partition four of the project pipelinespace corresponds to partition two of the DS2 pipeline space.

As shown, the partitions of the DS1 pipeline space and the DS2 pipelinespace have been effectively repartitioned under the new space of theproject pipeline. As part of the repartitioning, the partitions from DS1and DS2 are renumbered in a manner representing that the rows of DS2follow from the rows of DS1 (e.g., the append table DS2 partitions arenumbered to follow from the anchor table DS1 partitions).

As shown, each new partition inherits the data traversal program fromits corresponding DS1 or DS2 partition. For example, the referencestables and reference stacks are inherited. Because no data is moved orchanged, the reference stacks, which include references to the existingfile sets, remain the same in structure (e.g., where no new entry ispopped onto the top of the reference stack because of the appendoperation processing). One change is in the naming of the columns to befound in the file sets referenced by the reference stack. The columnnames, which originally referred to their original names in DS1 and DS2,are renamed to indicate the new common name for the appended columnsthat are mapped to each other. In some embodiments, a record/bookkeepingis maintained of the mapping between original column names and theircorresponding new names to which they refer. In this example, column C01of DS2 is appended to column C00 of DS1. Both columns are mapped to acommon column name, “C0.” Similarly, column C11 of DS2 is appended tocolumn C10 of DS1. Both columns are mapped to a common column name, “C1.”

In the above examples, the partitions were added under a newly declaredpipeline. In some embodiments, the partitions of the append table arepulled/incorporated into the pipeline of the anchor table, andrenumbered accordingly (i.e., the partitions of DS2 are repartitioned sothat they are consumed by DS1). For example, the partitions of DS2 arereassigned and incorporated into the DS1 pipeline, and are numbered suchthat they follow sequentially from the last partition number of the DS1partitions. In some embodiments, rather than creating a new name for thecolumns that are mapped to each other in the append, a column in theappend table assumes the name of the corresponding column in the anchortable (e.g., column C01 of DS2 assumes the name of column C00 of DS1when it is integrated into the DS1 pipeline).

The data from this new appended data set in the new pipeline is readusing the same techniques described above. In this example, the datatraversal program of each partition of the project space is executed toobtain an ordered subset of the appended results. The subsets arecombined together and ordered by corresponding partition numbers toarrive at the overall appended result. As shown, when assembling theoverall result, data values will be pulled from file sets that wereoriginally written for two different data sets (e.g., the file setsshown in FIG. 11C). While the appended result will have new column names“C0” and “C1,” when performing a lookup of the file sets, the maintainedmapping of the new column names to the original names in DS1 and DS2will be used to perform the lookup and obtain the appropriate columnvalues.

Thus, in the append operation, the processing described above creates avirtual representation of the appended data set, where the partitions(and corresponding data traversal programs) of the appended data setshave now been brought under a single logical space so that they will betreated altogether as a single data set. Further operations (e.g.,sequenced set of data preparation operations) can be performed on thenew logical single data set, an example of which will be describedbelow.

Append Example—Lowercase on DS2.C11 Prior to Append

As shown in the above examples, separate pipelines were originallydeclared for DS1 and DS2. In the following example, suppose that priorto performing the append, a lowercase operation was performed on columnC11 of DS2, while no further steps were performed on DS1 after beingimported.

Shown in the example of FIG. 11F is the state of the partitions andcorresponding data traversal programs of the DS1 pipeline space as ofthe import operation. Not shown are the corresponding file sets thatwere written when importing DS1.

Also shown in the example of FIG. 11F is the state of the partitions andcorresponding data traversal programs of the DS2 pipeline space as aresult of performing a lowercase on column C11 of DS2 after havingimported DS2. The file sets written due to the lowercase operations arealso shown. Not shown are the file sets written when importing DS2. Insome embodiments, the data traversal programs and file sets shown aregenerated using techniques similar to those described in conjunctionwith FIGS. 7A-8B.

DS1 and DS2, whose virtual representations prior to the append are shownin FIG. 11G (which correspond to their counterpart representations shownin FIG. 11F), are virtually appended by remapping/repartitioning, asdescribed above, the partitions in the DS1 and DS2 pipeline spaces to anew third “project” pipeline. The virtual representation of the resultsof the append operation are shown in FIG. 11H. Also shown is therenaming of columns in the reference stacks, whose structure, again, didnot change, as no data values were written or moved.

As shown in this example, partitions zero through one of the DS1pipeline were remapped to partitions zero through one, respectively ofthe new project pipeline. Partitions zero through two of the DS2pipeline were remapped to partitions two through four, respectively, ofthe new project pipeline. Because an additional lowercase operation hasbeen performed on column C11 of DS2 prior to the append, the referencestacks of partitions two through four have more entries than in projectpartitions zero through one. Additionally, the references tables forpartitions two through four include an additional column as compared tothe references tables for partitions zero through one. Thus, thepartitions in the same pipeline have different reference stacks andreferences tables. This reflects the histories of the data sets prior tohaving been appended.

When reading the result of the append, the partitions of the projectpipeline space are read using the same techniques described above (e.g.,in conjunction with FIGS. 7B and 8B). For example, a partition of theproject pipeline (representing operations on a single (virtual) dataset) is accessed. The data traversal program for the partition isobtained. References, file handles, and columns to look up are obtainedfrom the data traversal program. These items are used together todetermine a file hash (or any other file name representation) to locatea file set. A lookup is performed on the found file set to obtain thevalues for the specified columns. By doing so, a subset of thecumulative results represented by the data traversal program of apartition is obtained. Subsets of the cumulative results obtained fromvarious partitions are combined together according to partition order.

Append Example—Lowercase on Proj.C1 (After Append)

In the above example of FIGS. 11F-H, a lowercase on column C11 of theDS2 operation was performed on DS2 before it was appended to DS1. Thefollowing is an example that continues from the example of FIGS.11A-11E, in which DS1 and DS2 were appended directly after having eachbeen imported. In this example, a lowercase operation on the newproject's column C1 is performed after DS1 and DS2 have been appended.

The representation of the result of performing the lowercase on columnC1 of the project is shown in FIG. 11I. In this example, all of thepartitions of the project were affected by the lowercase operation, andthus all of the data traversal programs (including the references tablesand references stacks) were updated (from the state of the virtualrepresentation in FIG. 11E) to reflect the result of the lowercaseoperation.

Cache Fingerprint Example

Suppose, for example, that a first user had previously performed andsaved/cached the results of having performed the lowercase on DS2.C11,prior to append, as shown in FIGS. 11F-H. Suppose, for example, that thesignature/fingerprint attached to the cached representation indicatesthe steps that were performed that lead to the cached results (e.g., thesignature is a hash of the operations, or a concatenation of the stringrepresentations of the operations that led to the cached results, etc.).In some embodiments, the fingerprint can be used to produce the treestructure 1150 shown in FIG. 11J, which shows the pipeline of an importDS2 step followed by a lowercase on column C11 of DS2.

Suppose that the next day, a second user uses a step editor interface tospecify that they would like to append DS2 to DS1 and then perform alowercase on the resulting C1 column, which is the sequenced set of datapreparation operations that resulted in the generation of therepresentations described in conjunction with FIG. 11E.

Although the ordering of operations and the results of the differentsequences of operations specified by the two users differs, beforeperforming the second sequenced set of operations specified by thesecond user, it can be determined whether the previously cachedrepresentation can be leveraged to provide at least some or all of theresults.

The following is an example of using signatures/fingerprints todetermine whether an existing cached representation can be reused.Suppose, for example, that the second sequenced set of operationsspecified by the second user is used to derive a signature thatcorresponds to tree 1160 of FIG. 11K. The tree representation 1150 ofthe previously cached representation is also obtained. The trees can becompared to determine whether the graph or any subgraphs/paths matchbetween the two. A match indicates that a cached representation for someportion of the second sequenced set of operations exists.

In this example, no direct match is found between 1160 and 1150. In someembodiments, tree 1160 can be further manipulated to determine anequivalent tree that can then also be compared to 1150. For example, anoperator push down can be performed on 1160. In this example, thelowercase operation of 1160 is pushed down below the append to producetree 1170. Trees 1160 and 1170 are functionally/semantically equivalent,in that performing a lowercase on column C1 of the data set resultingfrom appending DS1 and DS2 is the same as having performed the lowercaseoperation on C10 of DS1 and C11 of DS2 first before performing theappend.

When comparing trees 1170 and 1150 together, it is determined thatsubgraph 1172 of 1170 matches to 1150. For example, a signature forportion 1172 (e.g., hash of the operations in portion 1172) matches tothe signature for the cached results 1150 (e.g., an equivalent hash hasbeen identified).

The cached result associated with the signature representing tree 1150can then be obtained. In this example, the cached result associated withsignature 1150 is associated with performing a lowercase operation onthe values in column C11 of DS2. The cached result can then be leveragedto reduce the amount of computation to perform the second sequenced setof operations. For example, because a cached result associated withperforming a lowercase operation on the values in column C11 of DS2exists, a lowercase operation need only be performed on the values incolumn C10 of DS1, rather than computing the lowercase on all values inC10 of DS1 as well as the values in C11 of DS2. This reduces the amountof writing that needs to be performed. The results of the lowercaseoperation on C10 of DS1 can then be appended with the cached results toobtain the result desired by the second user.

Join

Described below is an example embodiment of processing associated with ajoin operation. While a full outer join is shown in the followingexamples, the techniques described herein can be adapted accordingly toperform any other type of join (e.g., Cartesian joins).

FIG. 12A illustrates an example of data sets to be joined. In thisexample, suppose that a user would like to perform a full outer join ofdata set DS1 (1202) and data set DS2 (1204) on columns J1 and J2, withDS1 as the anchor/driving table and DS2 as the lookup table (i.e., DS2is joined to DS1), which will result in joined table 1206. The joinoperation can be specified, for example, by a user via a step editoruser interface, examples of which will be described below.

FIG. 12B illustrates an example of imported data. Continuing with theexample of FIG. 12A, data sets DS1 and DS2 have been partitioned andimported into respective DS1 and DS2 pipeline spaces as shown at 1210and 1220. Corresponding file sets written by each partition are alsoshown. Also shown are the current states (as of the import operation) ofthe data traversal programs (including references tables and referencestacks) for the partitions.

In this example, DS1 has been partitioned into two partitions, partitionzero and partition one, as shown. Partition zero of the DS1 pipeline1210 includes references table 1212 and corresponding reference stack1214. The data traversal program including references table 1212 andcorresponding reference stack 1214 represents the top two rows of DS1.Partition one of the DS1 pipeline 1210 includes references table 1216and corresponding reference stack 1218. The data traversal programincluding references table 1216 and corresponding reference stack 1218represents the bottom two rows of DS1.

In this example, DS2 has been partitioned into two partitions, partitionzero and partition one, as shown. Partition zero of the DS2 pipeline1220 includes references table 1222 and corresponding reference stack1224. The data traversal program including references table 1222 andcorresponding reference stack 1224 represents the top row of DS2.Partition one of the DS2 pipeline 1220 includes references table 1226and corresponding reference stack 1228. The data traversal programincluding references table 1226 and corresponding reference stack 1228represents the bottom three rows of DS2.

As in the example of append, a new pipeline is declared to represent thecombined result of the join. In the example of the full outer join, thenew pipeline space (referred to herein as the “project” pipeline) willinclude the same number of partitions as the aggregate number ofpartitions across the DS1 and DS2 pipeline spaces. An example embodimentof a process for arriving at the full outer join will be described belowin conjunction with FIGS. 12C-E.

FIGS. 12C-E illustrate an example embodiment of a process for performinga full outer join. In some embodiments, the full outer join is performedby performing a left outer join and a right anti-join, with the resultsappended together to generate the virtual representation of the fullouter join result. In the following nine steps described below, thefirst four steps are used to perform the left outer join. Steps fivethrough eight are used to perform the right anti-join. Step nine is usedto combine the results of the left and right joins to produce therepresentation of full outer join. The steps are described as follows.

Left Outer Join

FIG. 12C illustrates an example embodiment of a process for performing aleft outer join. In some embodiments, the results of the left outer joinare determined (and represented) by modifying/amending the datatraversal programs (i.e., the references tables and reference stacks) ofpartitions zero and one of the DS1 pipeline 1210 shown in FIG. 12B. Theprocessing performed in steps one through four is performed separatelyon each of the data traversal programs, but is shown together here forillustrative purposes.

At step one (1240), all DS1 rows are obtained. The rows of DS1 arerepresented by the references included in the references tables of thepartitions of the DS1 space (e.g., references tables of partitions zeroand one in DS1 pipeline space 1210 of FIG. 12B). In some embodiments,obtaining all DS1 rows includes obtaining the current references tablesfor each of the partitions of DS1.

For example, references table 1212 of partition zero of the DS1 pipelinespace 1210 of FIG. 12B is obtained and shown above double line 1242.Similarly, the references table 1216 of partition one of the DS1pipeline space 1210 is obtained and shown below line 1242.

At step two (1244) a column of J1 values corresponding to therows/references obtained at step one is populated. For example, a columnis added to the right of each of references tables 1212 and 1216 and ispopulated with corresponding J1 values, resulting in tables 1246 and1248, respectively. In some embodiments, the J1 values are obtained byexecuting the data traversal programs shown in partitions zero and oneof the DS1 pipeline space 1210 as shown in FIG. 12B.

At step three (1250), DS2 references for each J1 value are shown. Inthis step, the rows of DS2 (represented by their correspondingreferences) that include, in the J2 column, values matching to those incolumn J1 of DS1 are found. The identified rows are represented byreferences as indicated in the references tables of the partitions ofthe DS2 pipeline space 1220 of FIG. 12B.

In this step, the rows in DS1 and DS2 that share the same value in theirrespective J1 and J2 values are identified and mapped together. Theserows will be concatenated together horizontally to create a joined row.In this example, the mapping is performed in part by adding anadditional column (or columns if a row in DS2 is represented usingmultiple references) to the right of tables 1246 and 1248 to producetables 1252 and 1254, respectively. The columns are populated with theappropriate DS2 references that have been identified as described above.

As shown at 1254, there is no row in DS2 in which the J2 column has thevalue “C” (i.e., the top row of references table 1216 in partition oneof DS1 that is associated with the value “C” in its J1 column has nomatching counterpart in DS2). In this example, the absence of a matchingrow is represented by the “0” symbol (1256).

At step four (1258), the J1 values columns are dropped from tables 1252and 1254. For each of table 1252 and 1254, this leaves only the columnof DS1 references and the column of corresponding/matching DS2references remaining. The columns are concatenated together. In thisexample, the column containing DS2 values is concatenated to the left ofthe column containing DS1 values.

Thus, table 1252 is modified into table 1260, which is saved as the new,updated version of the references table for partition zero of the DS1pipeline. Similarly, table 1254 is modified into table 1262, which issaved as the new, updated version of the references table for partitionone of the DS1 pipeline. As each of the references tables for partitionsone and zero of the DS1 pipeline have been updated to include a newcolumn of corresponding DS2 references (that match according to the leftouter join condition as determined in steps one through three, above),the corresponding reference stacks are updated as well. In this example,the reference stacks of DS2 (shown at 1224 and 1228 of FIG. 12B) areconcatenated to the tops of reference stacks 1214 and 1218 of FIG. 12Bto generate updated reference stacks 1264 and 1266, respectively.

Thus, the data traversal programs of partitions zero and one of the DS1pipeline have been modified to represent the result of performing theleft outer join. As will be described in further detail below, as theleft outer join is an intermediary step in performing the full outerjoin, the updated partitions zero and one of DS1 will be repartitionedinto the new project pipeline via an append

Right Anti-Join

FIG. 12D illustrates an example embodiment of a process for performing aright anti join of the full outer join. In some embodiments, the processof FIG. 12D continues from the process of 12C. In some embodiments, theresults of the right anti join are determined (and represented) bymodifying/amending the data traversal programs (i.e., the referencestables and reference stacks) of partitions zero and one of the DS2pipeline 1220 shown in FIG. 12B. The processing performed in steps fivethrough eight is performed separately on each of the data traversalprograms, but is shown together here for illustrative purposes.

At step five (1268), all DS2 rows are obtained. The rows of DS2 arerepresented by the references included in the references tables of thepartitions of the DS2 space (e.g., references tables of partitions zeroand one in DS2 pipeline space 1220 of FIG. 12B). In some embodiments,obtaining all DS2 rows includes obtaining the current references tablesfor each of the partitions of DS2.

For example, references table 1222 of partition zero of the DS2 pipelinespace 1220 of FIG. 12B is obtained and shown above double line 1270.Similarly, the references table 1226 of partition one of the DS2pipeline space 1220 is obtained and shown below line 1270.

At step six (1272) a column of J2 values corresponding to the column ofDS2 rows/references obtained at step five is populated. For example, acolumn is added to the right of each of references tables 1222 and 1226and is populated with corresponding J2 values, resulting in tables 1274and 1276, respectively. In some embodiments, the J2 values are obtainedby executing the data traversal programs shown in partitions zero andone of the DS2 pipeline space 1220 as shown in FIG. 12B.

At step seven (1278) tables 1274 and 1276 are filtered to identify DS2rows where there is no corresponding DS1 row (represented usingreferences) whose J1 column value matches to a DS2 J2 column value. Inthis example, no references in table 1274 survived, resulting in anempty table 1280. Only one row of table 1276 remains, resulting in table1282.

At step eight (1284), the J2 values column of tables 1280 and 1282 areremoved, leaving in each table only the DS2 references that remained (ifany) as a result of the filtering operation in step seven. Thus, table1280 is modified into empty table 1286, which is saved as the new,updated version of the references table for partition zero of the DS2pipeline (represented with a “0” symbol). Similarly, table 1282 ismodified into table 1288, which is saved as the new, updated version ofthe references table for partition one of the DS2 pipeline. In thisexample, the newly updated references for partitions zero and one of DS2still obtain DS2 references, and the reference stacks for thosepartitions are not modified (e.g., are the same as shown at 1224 and1228 of FIG. 12B).

Thus, the data traversal programs of partitions zero and one of the DS2pipeline have been modified to represent the result of performing theright anti-join. As will be described in further detail below, as theright anti join is an intermediary step in performing the full outerjoin, the updated partitions zero and one of DS2 will be repartitionedinto the new project pipeline.

Determining the Representation of the Full Outer Join Result

FIG. 12E illustrates an example embodiment of a process for performing afull outer join. In some embodiments, the process of FIG. 12E continuesfrom the process of 12D.

At step nine (1290), the results of step four and step eight describedabove are appended together. In some embodiments, the appending isperformed similarly to as described in conjunction with FIGS. 11A-I. Forexample, the partitions of DS1 and DS2 are repartitioned into a newlydeclared pipeline (referred to as the “project” pipeline), which alsoincludes renumbering the partitions in sequential order in the newpipeline.

In this example, because DS1 is the driving table, partition zero of DS1as of step four is repartitioned as partition zero of the new projectpipeline, and includes the data traversal program including referencestable 1260 and corresponding reference stack 1264 as shown in FIG. 12C.Partition one of DS1 as of step four is repartitioned as partition oneof the new project pipeline, and includes references table 1262 andcorresponding reference stack 1266 as shown in FIG. 12C.

In this example, because DS2 is the lookup table, partition zero of DS2as of step eight is repartitioned as partition two of the new projectpipeline, and includes the data traversal program including referencestable 1286 and corresponding reference stack as shown in FIG. 12D.Partition one of DS2 as of step eight is repartitioned as partitionthree of the new project pipeline, and includes the data traversalprogram including references table 1288 and corresponding referencestack as shown in FIG. 12D.

In the above, the processing of FIGS. 12C (left outer join) and 12D(right anti-join) was described sequentially. In some embodiments, theprocessing of FIGS. 12C and 12D is performed in parallel. The results ofthe left outer join and right anti join are then appended together todetermine the representation of the full outer join result as describedabove in conjunction with FIG. 12E.

As shown in the example virtual representation of the result of the fullouter join shown in FIG. 12E, the reference stacks for partition zeroand one of the project pipeline each include references to file sets andsteps from disjoint sources. For example, the reference stacks for theproject partitions zero and one each include handles for file sets thatwere generated both for the DS1 pipeline as well as the DS2 pipeline.

As described above, using the techniques described herein, a set ofsequenced operations on one or more input data sets results in a virtualrepresentation of the results of the operations on the data sets. Thevirtual representation includes data traversal programs, which whenexecuted, output the actual data values of the results.

Additional Join Example—Lowercase on J2 of DS2 before Join

In the following example, suppose that a user decides to perform alowercase on column J2 of DS2 before it is joined with DS1. The state ofthe data traversal programs of the partitions of the DS1 and DS2pipeline spaces prior to the join are shown in FIG. 12F.

In this example, no rows in DS2 will have J2 values that match to J1values in the DS1 rows. By performing steps one through nine asdescribed above in conjunction with FIGS. 12C-E, the result of the fullouter join is represented as shown in FIG. 12G.

As shown above, the techniques described herein, such as the use of arepresentation such as a data traversal program, have various benefits.One example is an increase in the efficiency of storage, where theamount of storage needed to represent the results of operations isreduced. This is for example due to a compact data traversal programrepresentation of the results being maintained, rather than actualvalues of a data set. As another example, the efficiency in processingspeed is also increased, as only data that is modified by operations iswritten. Furthermore, by performing operations on references thatrepresent data, rather than the actual data itself, further efficiencygains can be realized, as the references are more compact than the dataitself (e.g., a set of references representing a row of data takes lessspace than the data values that make up the row). Additionally, byperforming caching, as described above, as well as identification ofcaches, as described below, redundancy can be avoided, where, forexample, existing cached results can be leveraged to avoid repeatingcomputations.

FIG. 13 is a flow diagram illustrating an embodiment of a process forcaching transformation results. In some embodiments, process 1300 isexecuted by data transformation engine 210 and caching engine 212 ofFIG. 2. The process begins at 1302 when a data traversal program thatrepresents a result of a set of sequenced data preparation operationsperformed on one or more sets of data is generated. In some embodiments,the set of sequenced data preparation operations form a pipeline throughwhich the input data is pushed. In some embodiments, the data traversalprogram indicates how to assemble one or more affected columns in theone or more sets of data to derive the result. In some embodiments, theone or more sets of data are re-written as an addressable data set. Forexample, the one or more sets of data are re-written as column files, asdescribed above, which are columns of cells stored in a file. In someembodiments, the values of the column files are obtained from thesources of the one or more data sets. As operations are performed, newversions of column files are written for those columns that are affected(e.g., modified/changed) by an operation. In some embodiments, the setof sequenced data preparation operations is received in the form of ascript (e.g., generated by script generator 204 of FIG. 2). In someembodiments, the script is generated based on user input received via astep editor user interface (e.g., provided by user interface engine202). The step editor user interface provides a user interface by whicha user can configure a sequenced set of data preparation operations tobe performed on one or more input sets of data.

The data traversal program records the cumulative effects of performingthe set of sequenced data preparation operations. In some embodiments,as described above, the data traversal program includes references(e.g., stored in references tables). The references are references tomappings of row transformations that occurred during the set ofsequenced data preparation operations. In some embodiments, thereferences refer to data values (e.g., in column files) that are used todescribe/define a row in the result. In some embodiments, the datatraversal program includes a reference stack. The reference stackincludes a record/history of the sequenced operations and columns thatwere changed by the sequenced set of operations. In some embodiments,the reference stack includes references to file sets that store columnfiles of data values that were written due to data preparationoperations that were performed.

In some embodiments, the data traversal program requires lessstorage/memory than what is required to store the result. In someembodiments, the data traversal program is generated without moving theset of data. In some embodiments, the data traversal program isgenerated without generating the result.

In some embodiments, the manner in which the data traversal program isgenerated/updated throughout a sequenced set of operations is operationdependent, as described in the various data preparation operationexamples above. Example techniques for generating and executing datatraversal programs are described in the examples above.

At 1304, the data traversal program that represents the result isstored. For example, the data traversal program is cached to a cachelayer. In some embodiments, data pertaining to the data traversalprogram, such as a references table is stored. In some embodiments, thedecision of whether to store/cache a data traversal program can be basedon a variety of factors. For example, a user can explicitly indicate(e.g., via an editor user interface) where in a sequenced set ofoperations that they would like to create a save point. The cacherepresentation corresponding to that save point location will then bestored. In some embodiments, rather than storing the data traversalprogram, the data traversal program is maintained in memory.

In some embodiments, the decision of whether to cache a representationis based on the data operation that was performed. For example, thecomplexity/computational cost of an operation/set of operations can beconsidered. As one example, for costly/expensive operations, such assort, filter, or join that affect an entire set, the resulting datatraversal program can be cached. As another example, the cost of anaggregate set of operations can be considered. For example, while thecost of an individual operation, such as performing an uppercase, may beinexpensive, performing multiple of the operation (e.g., uppercases ontwenty columns) may be costly. Thus, the contents of a script can beevaluated to determine where caching should be performed.

Another example factor that can be considered includes a measure of thelikelihood that a user may revise an operation. For example, byobserving, over time, various users' behaviors, the types of operationsthat are often changed or swapped out in scripts can be identified andlearned.

By caching the representations at various stages of the pipeline, userscan, for example, return to view the results of a certain point in apipeline without recomputing the sequenced set of operations that led upto that point.

In some embodiments, the data traversal program is stored with a set ofone or more corresponding signatures. In some embodiments, the set ofone or more signatures is derived based on the set of sequencedoperations that were performed. For example, each signature is generatedusing a hash function (e.g., a cryptographic hash such as MD5, SHA-1 orsome other signature generating function). of the operations that wereperformed, where the operations are combined in a manner that preservesthe order in which they were applied. Signatures are described infurther detail below with respect to process 1400 of FIG. 14.

In some embodiments, the data traversal program representing the resultcan be recomputed and updated. For example, suppose that the user hasperformed a set of sequenced operations on a source dataset DSX. Thenext morning, another user makes a change to the source dataset DSX. Inresponse to an indication that the source dataset DSX has been changed,the data traversal program can be updated by re-performing the set ofsequenced operations on the modified source dataset (i.e., a new cacheis built using the newer version of the data, allowing for automaticupdating of caches).

At 1306, a specification of the set of sequenced operations to beperformed on the one or more sets of data is received. At 1308, the datatraversal program that represents the result is accessed. In someembodiments, a stored copy of the data traversal program that representsthe result is accessed. In some embodiments, the data traversal program(or copy of) is accessed in response to receiving the specification at1306. As one example, a user further performs data preparation stepsbeyond those that result in the data traversal program being generated.The user decides that they would like to go back to the stage in thepipeline at which the generated data traversal program wasstored/cached. This indicates that the user would like to perform thesame set of sequenced operations. The cached data traversal program isthen retrieved.

As another example, another user happens to configure (e.g., via a stepeditor user interface) a same (or equivalent) sequenced set of datapreparations as was performed to generate the cached data traversalprogram. A signature is derived from the received specification of theset of sequenced operations. The signature is determined to match to thesignature of the cached data traversal program. The matching cached datatraversal program is then obtained. Further details regarding the use ofsignatures to obtain cached results are described in conjunction withprocess 1400 of FIG. 14.

At 1310, the one or more affected columns in the one or more sets ofdata are assembled according to the data traversal program to generatethe result. Examples of executing data traversal programs are describedabove in conjunction with FIGS. 7B and 8B. At 1312, the result isoutputted. In some embodiments, outputting the results includespublishing or exporting them to another file. In some embodiments,outputting the results includes displaying the results. In someembodiments, only those results that are viewable in a current window ofa UI are displayed. For example, if a result includes one thousand rows,but only three hundred rows are viewable in a UI, only those threehundred rows are assembled using the data traversal program. (More rowscan be assembled to accommodate for potential scrolling by the userthrough the results). In some embodiments, the rows that are visible tothe user determine the amount of computation to be performed. Forexample, rather than performing data preparation operations on all ofthe data, the operations are performed only on those rows that arevisible to a user. As one example, a determination is made as to whatrows are viewable to the user (e.g., what rows are viewable in a userinterface). Data preparation operations are only performed on thosepartition(s) that include (references to) the rows currently viewable bythe user. This reduces the amount of calculation load while stillproviding the results that the user desires.

In some embodiments, as described above, process 1300 is performed inthe context of a distributed computing environment (e.g., Sparkdistributed computing platform), where the one or more data sets to beoperated on (transformed through a pipeline/sequenced set of datapreparation operations) are divided into partitions (e.g., using process500 described in FIG. 5) to be worked on (e.g., by pipeline executors,as described above).

In some embodiments, each partition includes its own data traversalprogram, which when executed provides a subset of the overall results ofapplying a set of sequenced data preparation operations to one or moresets of data.

One example embodiment of the processing performed at 1310 to assemble aresult in such a distributed computing platform using data traversalprograms is as follows. A subset of the cumulative results at a stage inthe pipeline is obtained by accessing a partition. The data traversalprogram for the partition is obtained and executed. A set of referencesrepresenting a row of the subset of results is obtained from areferences table of the data traversal program. Each reference comprisesa coordinate identifying a partition number and a row identifier. Acoordinate is used in conjunction with an entry of a reference stack toidentify and access a previously written file set. The file set includesa set of columns that were modified as a result of performing anoperation. The row identifier is used to identify the row in a specifiedsubset of the columns that was written to the file set. The values inthat row for the specified subset of columns are obtained. The columnsto be looked up are specified in the reference stack entry. Thus, one ormore affected columns in the one or more sets of data are assembledaccording to the data traversal program.

The overall results as of the stage of the pipeline are determined byaggregating and collating the different subsets of results (e.g., by apipeline master, as described above), where the various subsets ofresults obtained from the partitions are organized in a particular order(e.g., by partition order, as described above).

Knowledge of the location of different subsets of the result can bemanaged by a pipeline master. This can be used to perform optimizationswhen providing output. For example, when determining what window ofresults to provide in the UI to a user (e.g., as they are scrollingthrough a result), only those subsets of results corresponding to thecurrent position of the user in the overall results are obtained fromtheir corresponding partitions.

FIG. 14 is a flow diagram illustrating an embodiment of a process forcache reuse. In some embodiment, process 1400 is executed by datatransformation engine 210 and caching engine 212 of FIG. 2. The processbegins at 1402 when a first set of sequenced data preparation operationsis performed on one or more sets of data to generate a plurality oftransformation results. In some embodiments, a data preparationoperation is an operation that transforms/mutates an input data. In someembodiments, the data is accessible dynamically upon execution of theset of sequenced operations, where the data is not necessarily stored,but may be computed on-the-fly, as needed. This is in contrast tooperating against data stored at a fixed and known location. Further,the first set of sequenced operations is performed without theadvantages of the input having been previously indexed and partitioned.In various embodiments, data preparation operations include clustering,joining, appending, sorting, uppercase, lowercase, filtering,deduplicating, grouping by, adding or removing columns, adding orremoving rows, pivoting, depivoting, order dependent operations, etc. Insome embodiments, the plurality of transformation results includes datatraversal programs, such as those described in the examples above and inprocess 1300 of FIG. 13.

At 1404, one or more of the plurality of transformation results and oneor more corresponding operation signatures are cached. In someembodiments, a cached operation signature is derived based at least inpart on a subset of sequenced operations that generated a correspondingresult. One example of a signature is a hash of the subset of sequencedoperations. In some embodiments, the cached operation signaturecomprises an order independent grouping of representations of the subsetof sequenced operations that were performed to arrive at thecorresponding result. For example, the signature is a grouping of(hashed) identifiers (e.g., serial numbers, string representations,etc.) representing the subset of sequenced operations. In someembodiments, the grouping can be order-dependent. In some embodiments,having a signature based on a grouping of operation representationsallows for collective comparisons with other groupings of operationrepresentations, for example, to determine if there is any overlapbetween different groups of data preparation operations (e.g., specifiedin different sets of sequenced operations). In some embodiments, thecached operation signature is also derived based on a reference to theset of data that was operated on. For example, the cached operationsignature can also be generated based on an identifier and/or versionnumber of the set of data that is operated on. In some embodiments, thetransformation results include data traversal programs, such as thosedescribed above.

At 1406, a specification of a second set of sequenced operations isreceived. For example, via a user interface, a user creates the newsecond set of sequenced operations or manipulates an existing set ofsequenced operations. At 1408, an operation signature associated withthe second set of sequenced operations is determined.

At 1410, a cached result among the cached results is identified based atleast in part on the determined operation signature. For example, insome embodiments, the determined operation signature is compared withthe signatures corresponding to stored results. For example, thegroupings of operation representations associated with the signaturescan be collectively compared with each other to determine any overlap(e.g., partial or complete overlap) between the operations of thedetermined operation signature and the operations associated with thestored results.

In some embodiments, the signatures correspond to graph structures suchas those shown in FIGS. 11J-K that represent the flow of a set ofsequenced operations. Comparing different signatures includes comparingdifferent graph structures. In some embodiments, it is determinedwhether any or all of the signatures being compared match or areotherwise equivalent (e.g., sub-signatures can be identified). In someembodiments, operator push down, such as described above in conjunctionwith FIG. 11K, can be used to find matches. In some embodiments, theoperator push down generates functionally (semantically) equivalentsignatures. Thus, stored results that match to portions of the secondset of sequenced operations can be identified and leveraged as well.

At 1412, the cached result is outputted. In some embodiments, if thestored result is equivalent to the result of having performed the secondset of sequenced operations, then the identified stored result isoutputted directly (e.g., displayed in a UI or published/exported). Insome embodiments, if the identified stored result is a partial match andan intermediary result usable to obtain a desired final result, thenthat portion of the results is obtained and need not be computed. Thisreduces the amount of computation required to perform the second set ofsequenced operations, which can incorporate the identified stored resultto arrive at a final result.

Step Editor

FIGS. 15A-E illustrate example embodiments of user interfaces of a stepeditor usable to configure a sequence of data preparation operations andto view corresponding results. In some embodiments, the user interfaceexamples of FIGS. 15A-E are implemented by user interface engine 202 offront end 200 of FIG. 2.

Suppose for example that a user, via step editor UI 1500 of FIG. 15A,specifies a set of sequenced data preparation operations 1502. The setof sequenced operations starts at 1504, where a data set (called“Transactions” in this example) is specified. In some embodiments, thedata set is partitioned and imported using the techniques describedabove. A step in the set of sequenced operations can be edited tospecify criteria on which the step/action is performed. For example, atstep 1506, rows can be removed based on configurable filtering criteria.In some embodiments, the specified steps are used to generate a script(e.g., using script generator 204 of front end 200 of FIG. 2). Theoperations specified in the script are then performed, for example, bypipeline server 206 of FIG. 2 and/or pipeline server 300 of FIG. 3.

At 1508, results as of a particular step can be viewed. In this example,the result of having sequentially performed steps 1504-1506 is shown.The results can be determined using the techniques described above,where, for example, data traversal programs representing the result aregenerated. The data traversal programs can then be executed to outputthe corresponding results. By using such data traversal programs andoperating on references that are intermediate representations of theactual data set (rather than operating on the actual data itself), theresulting increase in computational efficiency as described above canimprove application response time, where for example, the results areprovided to the user in real-time, without the user having to wait longperiods of time for the operations to be performed. In some embodiments,only those results that are viewable in portion 1508 of the UI arecomputed and displayed, as described above. At 1510, the results as of aparticular step can also be published (e.g., exported).

The step editor user interface also provides the ability to go backwardsand forwards through the sequenced set of steps. Continuing with theexample of FIG. 15A, suppose that the user would like to go back to thethird step 1512 of FIG. B to see the data at that step. If the result atthat step was previously cached (e.g., at a corresponding save point),then the cached result can be retrieved and displayed at display region1514. For example, as the sequenced set of operations is performed, theresults as of step 1512 can be saved by the user (e.g., by pressing a“save” button corresponding to that stage of the pipeline), orautomatically saved (e.g., by a pipeline server such as pipeline server300 based on various cost functions and criteria as described above).

In some embodiments, if there was no save point for that step, it isdetermined whether there are any existing cached results that can beleveraged. For example, as described above, operation signatures (e.g.,hashes) can be generated for the current set of steps of interest andcompared against the signatures associated with cached results. If amatch is found, the matching cached result can be obtained so that thecomputations to arrive at the cached result need not be performed. Insome embodiments, matches that identify cached results that areintermediary results on the path to determining a final result can alsobe leveraged. For example, the intermediary result need not berecomputed, reducing the total amount of computation needed to arrive ata desired result. If no matches are found, then the current set of stepscan be executed to arrive at the desired result.

The user can also move forward again through the steps (e.g., to returnto some point in the pipeline after having previously traversedbackwards). Similarly to as described above, if the forward result hasbeen saved/cached, then it can be retrieved and provided as output. If acached result does not exist, then the results can be recomputed (e.g.,by determining a new data traversal program).

In some embodiments, the step editor provides the ability to mute a stepto see how data would look like with or without that step. Continuingwith the example of FIG. 15B, suppose that a user, via interface 1516 ofFIG. 15C, has indicated that they would like to mute the third step,1518 (which is the same third step 1512 of FIG. 15B). In someembodiments, a new script is generated for steps 1520 that does notinclude 1518. In some embodiments, the operations of the reduced set ofsteps are used to generate one or more operation signatures. Thegenerated signatures can be used to determine whether any existingcached representations can be leveraged. If not, then the new sequencedset of steps minus step 1512 of FIG. 15B is recomputed.

In one example embodiment, the signature generated based on the newsequenced set of steps is used to create a tree/graph representation ofthe new sequenced set of steps 1520 (with 1518 muted). This is comparedwith the tree/graph generated from the signatures of cached results.Using techniques similar to those described in conjunction with FIGS.11J-K, it can be determined whether there are any existing cachedresults that can be leveraged. For example, operator push downs can beused when determining potential matches.

The results of muting step 1518 can then be displayed, as shown at 1519.

In some embodiments, the step editor also provides the ability to deletea step. Continuing with the example of FIG. 15C, suppose that the user,after viewing the data with step 1518 muted, decides to remove thatstep. Portion 1524 of interface 1522 of FIG. 15D is updated to reflectthe removal of that step.

In some embodiments, the step editor also provides the ability to savechanges to the sequenced set of operations. For example, as changes to apipeline are made, each version of the pipeline can be saved as adifferent version of the project that is being worked on. For example,different versions of a project are shown at 1526 of FIG. 15E. In thisexample, the user has selected version 1528 to view. The correspondingpipeline for version 1528 of the project is shown at 1530. In thisexample, version 1528 was maintained by saving the state of the projectas of FIG. 15C, where the third step was muted. The results for version1528 of the project are shown at 1532.

FIG. 16 is a flow diagram illustrating an embodiment of a process forusing a step editor for data preparation. In some embodiments, process1600 is executed by pipeline server 206 of FIG. 2. The process begins at1602 when an indication of a user input with respect to at least some ofa set of sequenced data preparation operations on a set of data isreceived. For example, user inputs such as those described above (e.g.,muting a step, deleting a step, stepping backwards/forwards through theset of sequenced data preparation operations, etc.), are received. Insome embodiments, the user input is received via a user interface (e.g.,such as step editor user interfaces 15A-E described above) provided by afront end such as front end 200 of FIG. 2 (e.g., using user interfaceengine 202). In some embodiments, the user input results in amodification to, or a selection of, at least some of the datapreparation operations in the set of sequenced data preparationoperations. In some embodiments, a script is generated (e.g., usingscript generator 204 of front end 200 of FIG. 2) based on the set ofsequenced data preparation operations and the user input. In someembodiments, the set of sequenced data preparation operations is savedin response to the user input. For example, if a change to the sequencedset of data preparation operations is detected, then the new version ofthe sequenced data preparation operations is saved (e.g., versioning isperformed, as described above).

At 1604, a signature is generated based at least in part on the set ofsequenced data preparation operations and the user input. For example,if the user input modifies the set of sequenced data preparationoperations (e.g., by muting or deleting a step), then a signature basedon the modified set of sequenced data preparation operations isgenerated. As another example, if the user steps through the set ofsequenced data preparation operations (e.g., forwards or backwards) toview the results as of some particular stage in the pipeline (e.g., asof step three in a set of five sequenced data preparation operations),then a signature can be generated for the subset of the sequenced datapreparation operations up to the point indicated by the user. In someembodiments, the signature is generated based on the script that isgenerated in response to the user input with respect to the set ofsequenced data preparation operations.

In some embodiments, the signature is generated based on the set of databeing/to be processed. For example, references to/representations of theset of data are used to generate the signature. One examplerepresentation of the set of data is an identifier and version number ofthe set of data. For example, different sets of data can be associatedwith different identifiers. Different versions of the same set of datacan be associated with different version numbers. As will be describedin further detail below, signatures can be matched based on the set ofsequenced data preparation operations, the user input with respect tothe set of sequenced data preparation operations, and the representationof the set of data. For example, the same set of sequenced datapreparation operations applied to two different sets of data wouldresult in different signatures (and have different results as well).

At 1606, the generated signature is used to determine whether thereexists a cached result associated with the set of sequenced datapreparation operations, the user input, and the reference to the set ofdata. In some embodiments, the match determination and cached resultidentification is performed using the techniques described inconjunction with process 1400 of FIG. 14. For example, the generatedsignature is compared to signatures corresponding to cached results(represented by data traversal programs). Partial matches can also beidentified. Similarly, other techniques described above, such asoperation push down can also be used to identify matches. If anassociated cached result exists, then the process continues to 1608. Ifan associated cached result does not exist, then the process continuesto 1610.

At 1608, the matching associated cached result is retrieved. In someembodiments, the cached result is represented using a data traversalprogram, which is retrieved. In some embodiments, if the cached resultis equivalent to the result of having applied the user input to the setof sequenced data preparation operations, then the retrieved cachedresult is outputted directly (e.g., displayed in a step editor UI orpublished/exported) at 1612. In some embodiments, if the identifiedcached result is a partial match and an intermediary result usable toobtain a desired final result, then that portion of the results isobtained and need not be re-computed. This reduces the amount ofcomputation required to arrive at the final result. The final result canthen be computed using the retrieved data traversal program associatedwith the cached result and outputted at 1612.

At 1610, if no matching cached result exists, then a data traversalprogram representing the result of applying the user input to the set ofsequenced data preparation operations is generated (e.g., using theprocessing described above in conjunction with process 1300 of FIG. 13).The result represented by the generated data traversal program is thenprovided as output at 1612. For example, the results are published orexported (e.g., to an external file).

In some embodiments, the results are displayed to the user via stepeditor user interfaces such as those described above. In someembodiments, only those results that are viewable in a current window ofa UI are displayed. For example, if a result includes one thousand rows,but only three hundred rows are viewable in a UI, only those threehundred rows are assembled using the data traversal program. (More rowscan be included to accommodate for potential scrolling by the userthrough the results).

In some embodiments, the rows that are visible to the user can be usedto reduce the amount of computation to be performed. For example, ratherthan performing data preparation operations on all of the data, theoperations are performed only on those rows that are visible to a user.As one example, a determination is made as to what rows are viewable tothe user (e.g., what rows are viewable in a user interface). (More rowscan be included to accommodate for potential scrolling by the userthrough the results). Data preparation operations are only performed onthose partition(s) that include (references to) the rows currentlyviewable by the user. This reduces the amount of calculation load whilestill providing the results that the user desires. Thus, by onlyperforming operations on those rows that are visible to users, users areable to view real-time results as they interact with the step editoruser interfaces (e.g., while making changes to the data preparationoperations).

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A system, comprising: one or more processorsconfigured to: sequentially perform a first set of sequenced datapreparation operations on one or more input sets of data, whereinsequentially performing the first set of sequenced data preparationoperations transforms the one or more sets of data to generate aresulting data set that is different from the one or more input sets ofdata; cache a representation of the resulting data set usable tore-generate the resulting data set; cache a first operation signature,wherein the first operation signature is derived based at least in parton sequenced data preparation operations in the first set of sequenceddata preparations and the one or input sets of data; receive aspecification of a second set of sequenced operations; derive a secondoperation signature based at least in part on the sequenced datapreparation operations in the second set of sequenced operations; inresponse to determining a match between the first operation signatureand the second operation signature, use the cached representation tore-generate the resulting data set; and provide the re-generatedresulting data set as output; and a memory coupled to the one or moreprocessors and configured to provide the one or more processors withinstructions.
 2. The system recited in claim 1 wherein the first set ofsequenced data preparation operations comprises at least one ofclustering, joining, appending, sorting, uppercase, lowercase,filtering, deduplicating, grouping by, adding or removing columns,adding or removing rows, pivoting, or depivoting.
 3. The system recitedin claim 1 wherein the first operation signature comprises a hash of atleast a portion of the first set of sequenced data preparationoperations.
 4. The system recited in claim 1 wherein the first operationsignature comprises an order independent grouping of representations ofat least a portion of the first set of sequenced data preparationoperations.
 5. The system recited in claim 1 wherein determining thematch between the first operation signature and the second operationsignature comprises determining an overlap between the first operationsignature and the second operation signature.
 6. The system recited inclaim 1 wherein determining the match between the first operationsignature and the second operation signature comprises: manipulating thesecond operation signature to determine an equivalent operationsignature; and comparing the equivalent operation signature against thefirst operation signature.
 7. The system recited in claim 6 wherein theequivalent operation signature is determined at least in part byperforming an operator push down on the second operation signature. 8.The system of claim 1 wherein the representation of the resulting dataset comprises a data traversal program, and wherein the one or moreprocessors are configured to re-generate the resulting data set at leastin part by executing the data traversal program.
 9. The system of claim1 wherein providing the re-generated resulting data set as outputcomprises displaying, in a user interface, at least a portion of there-generated resulting data set.
 10. The system of claim 1 whereinproviding the re-generated resulting data set as output comprisesexporting at least a portion of the re-generated resulting data set. 11.A method, comprising: sequentially performing a first set of sequenceddata preparation operations on one or more input sets of data, whereinsequentially performing the first set of sequenced data preparationoperations transforms the one or more sets of data to generate aresulting data set that is different from the one or more input sets ofdata; caching a representation of the resulting data set usable tore-generate the resulting data set; caching a first operation signature,wherein the first operation signature is derived based at least in parton sequenced data preparation operations in the first set of sequenceddata preparations and the one or input sets of data; receiving aspecification of a second set of sequenced operations; deriving a secondoperation signature based at least in part on the sequenced datapreparation operations in the second set of sequenced operations; inresponse to determining a match between the first operation signatureand the second operation signature, using the cached representation tore-generate the resulting data set; and providing the re-generatedresulting data set as output.
 12. The method of claim 11 wherein thefirst set of sequenced data preparation operations comprises at leastone of clustering, joining, appending, sorting, uppercase, lowercase,filtering, deduplicating, grouping by, adding or removing columns,adding or removing rows, pivoting, or depivoting.
 13. The method ofclaim 11 wherein the first operation signature comprises a hash of atleast a portion of the first set of sequenced data preparationoperations.
 14. The method of claim 11 wherein the first operationsignature comprises an order independent grouping of representations ofat least a portion of the first set of sequenced data preparationoperations.
 15. The method of claim 11 wherein determining the matchbetween the first operation signature and the second operation signaturecomprises determining an overlap between the first operation signatureand the second operation signature.
 16. The method of claim 11 whereindetermining the match between the first operation signature and thesecond operation signature comprises: manipulating the second operationsignature to determine an equivalent operation signature; and comparingthe equivalent operation signature against the first operationsignature.
 17. The method of claim 16 wherein the equivalent operationsignature is determined at least in part by performing an operator pushdown on the second operation signature.
 18. The method of claim 11wherein the representation of the resulting data set comprises a datatraversal program, and wherein the one or more processors are configuredto re-generate the resulting data set at least in part by executing thedata traversal program.
 19. The method of claim 11 wherein providing there-generated resulting data set as output comprises displaying, in auser interface, at least a portion of the re-generated resulting dataset.
 20. The method of claim 11 wherein providing the re-generatedresulting data set as output comprises exporting at least a portion ofthe re-generated resulting data set.
 21. A computer program productembodied in a non-transitory computer readable storage medium andcomprising computer instructions for: sequentially performing a firstset of sequenced data preparation operations on one or more input setsof data, wherein sequentially performing the first set of sequenced datapreparation operations transforms the one or more sets of data togenerate a resulting data set that is different from the one or moreinput sets of data; caching a representation of the resulting data setusable to re-generate the resulting data set; caching a first operationsignature, wherein the first operation signature is derived based atleast in part on sequenced data preparation operations in the first setof sequenced data preparations and the one or input sets of data;receiving a specification of a second set of sequenced operations;deriving a second operation signature based at least in part on thesequenced data preparation operations in the second set of sequencedoperations; in response to determining a match between the firstoperation signature and the second operation signature, using the cachedrepresentation to re-generate the resulting data set; and providing there-generated resulting data set as output.